mozilla-releng / mozilla-releng/scriptworker
download artifacts with temp_queue if possible
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 39
- Avg merge
- 4h 18m
- Merged PRs (30d)
- 6
Description
We currently download artifacts with queue, which uses the worker creds. This means for private artifacts, the worker clientId needs to have access to those private artifacts.
The temp_queue will be given access to private artifacts for those tasks that need them. So if we download artifacts with that, we no longer need to add private artifact support to the worker clientId. Let's do that.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the artifact download path that currently uses queue, then compare how temp_queue is made available to tasks needing private artifacts. The work is done when those downloads use temp_queue and no longer require private-artifact access for the worker clientId; check the existing artifact-related tests if available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100