From Fedora Project Wiki
(invocation concerns) |
Martinpitt (talk | contribs) (absolute paths are fixed) |
||
| Line 1: | Line 1: | ||
In invocation why would I want to hardcode absolute paths for test execution, artifacts, logs, | # In invocation why would I want to hardcode absolute paths for test execution, artifacts, logs, This should be a relative path so where ever you run things it is in the local workspace. My machine, Jenkins, taskotron, etc. | ||
This should be a relative path so where ever you run things it is in the local workspace. My machine, Jenkins, taskotron, etc. | #* MartinPitt: I reworked the invocation; it was also impractical for tests that run as non-root, and it would have potentially clobbered the root directory with temporary stuff. | ||
Revision as of 09:18, 28 March 2017
- In invocation why would I want to hardcode absolute paths for test execution, artifacts, logs, This should be a relative path so where ever you run things it is in the local workspace. My machine, Jenkins, taskotron, etc.
- MartinPitt: I reworked the invocation; it was also impractical for tests that run as non-root, and it would have potentially clobbered the root directory with temporary stuff.