Closed
Bug 1241927
Opened 9 years ago
Closed 7 years ago
Firefox build tasks via TC reference an unknown task via the build link on Treeherder ("Artifact not found")
Categories
(Taskcluster :: Services, defect)
Taskcluster
Services
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: whimboo, Unassigned)
References
Details
When you select a Firefox build as created via Taskcluster in Treeherder like the following one:
https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&selectedJob=3142932
you will see a `build` link at the lower left corner. When you click on that you should usually get to the appropriate build folder with all the artifacts produced by the build task. Sadly the link redirects to an unknown task?
https://queue.taskcluster.net/v1/task/Q-YILfEsQfW6euKH1ktwCg/runs/0/artifacts/public/logs/
Reporter | ||
Comment 1•9 years ago
|
||
Greg said on IRC that integration might be the better component here.
Component: Task Configuration → Integration
Updated•8 years ago
|
Component: Integration → Platform and Services
Reporter | ||
Comment 2•8 years ago
|
||
These days we end-up with a 403 forbidden failure:
https://treeherder.allizom.org/#/jobs?repo=try&revision=fa48dadee6e9&selectedJob=26140000
Clicking on build gives me:
https://queue.taskcluster.net/v1/task/PnwWXZOuT8CFZ8TkL0G0CA/runs/0/artifacts/
Comment 3•8 years ago
|
||
We do not have a file browser similar to an ftp server or anything. The best we have is listing the artifacts as we do in the task inspector, we also include a list of links in the job details tab for convenience as well that should work.
I'm not sure how that build link is created, as far as I know it's not something taskcluster provided.
Reporter | ||
Comment 4•8 years ago
|
||
AFAIR it takes the log URL, and extracts the directory.
Log URL:
https://queue.taskcluster.net/v1/task/PnwWXZOuT8CFZ8TkL0G0CA/runs/0/artifacts/public%2Flogs%2Flive.log
Given that this appropriate code might have the same issue as mozharness (bug 1295948) we end-up with:
https://queue.taskcluster.net/v1/task/PnwWXZOuT8CFZ8TkL0G0CA/runs/0/artifacts/
Maybe it should really be a property which should be set. Automatically determining the URL doesn't seem to work at all. Lets see what Cameron says.
Flags: needinfo?(cdawson)
Comment 5•8 years ago
|
||
This is really a dupe of bug 1060649.
The automatically derived build directory URL doesn't work in a non-buildbot world.
Flags: needinfo?(cdawson)
Reporter | ||
Comment 6•8 years ago
|
||
Well, not a dupe. It would need changes in taskcluster so such a new property gets also set. Marking as dependency instead.
Depends on: 1060649
Comment 7•7 years ago
|
||
Found in triage.
We think this is fixed. All the artifacts are listed in the Job Details pane.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 8•7 years ago
|
||
Build is no longer a link and we show all the artifacts now. So this is indeed fine.
Assignee | ||
Updated•6 years ago
|
Component: Platform and Services → Services
You need to log in
before you can comment on or make changes to this bug.
Description
•