docker http build should use the tag of the pipeline run, not the latest tag
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 570
- Forks
- 351
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 65
Description
In https://community-tc.services.mozilla.com/tasks/B2oxyx2wSbmYzouCZLw18Q/runs/1/logs/public/logs/live.log, the task was run with v0.0.596. While the pipeline was running, we released v0.0.598.
The task should have downloaded models corresponding to the v0.0.596 pipeline run, but instead it tried to retrieve v0.0.598 models and failed because there was no run corresponding with v0.0.598.
It was actually a good failure, because if we had done a run with v0.0.598, then this task would have picked up a model from v0.0.598 while it was running v0.0.596 code.
We should make sure the task picks up the right version.
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
Start with the Docker HTTP build pipeline and the attached live_backing.log, then trace how the pipeline run version is selected when models are downloaded. Confirm the task uses the run's v0.0.596 tag rather than the latest release, and verify that model retrieval remains tied to the code version running the task.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- devops, machine-learning
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100