Closed
Bug 1466217
Opened 7 years ago
Closed 7 years ago
Restore mozharness config to build logs or make localconfig.json visible in build artifacts
Categories
(Testing :: General, enhancement)
Tracking
(firefox62 fixed)
RESOLVED
FIXED
mozilla62
| Tracking | Status | |
|---|---|---|
| firefox62 | --- | fixed |
People
(Reporter: gbrown, Assigned: gbrown)
References
Details
| Assignee | ||
Comment 1•7 years ago
|
||
It seems most build tasks use the 'upload' build target to copy artifacts to the path given by env variable UPLOAD_PATH, typically equal to /builds/worker/artifacts on linux.
| Assignee | ||
Comment 2•7 years ago
|
||
I cannot find a reasonably reliable way of making localconfig.json available as an artifact across all mozharness tasks. For instance, mozharness currently has no knowledge of /builds/worker/artifacts (build tasks just link to it through UPLOAD_PATH, which isn't known to the scripts themselves), and I don't see an easy way of adding localconfig.json to the taskcluster artifact configuration that I'd be confident in applying universally. So I'm just going to revert the dump_config change, so that the mozharness config is normally dumped to all mozharness logs.
Pushed by gbrown@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/426d58b56d6f
Restore dump of mozharness config to test and build logs; r=me,a=test-only
Comment 4•7 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox62:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla62
You need to log in
before you can comment on or make changes to this bug.
Description
•