If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

tooltool.py to be included in (gecko) docker build images

NEW
Unassigned

Status

Taskcluster
Platform and Services
2 years ago
a year ago

People

(Reporter: pmoore, Unassigned)

Tracking

Details

See https://bugzilla.mozilla.org/show_bug.cgi?id=1198173#c23 for context.

Basically we should include tooltool.py in docker image rather than cloning git.mozilla.org / github.com for each task execution.

NB: if tooltool.py needs updating, we would now need to bump VERSION of docker images in-tree, and publish the new binaries to whichever registry/registries they can be downloaded from. A new tooltool.py won't get picked up automatically.
Also, we should try to avoid relying on github.com availability in tasks, where we have mirroring set up for git.mozilla.org, since it can place a strain on github.com that may cause them to block access.
(In reply to Pete Moore [:pmoore][:pete] from comment #0)
> NB: if tooltool.py needs updating, we would now need to bump VERSION of
> docker images in-tree, and publish the new binaries to whichever
> registry/registries they can be downloaded from. A new tooltool.py won't get
> picked up automatically.

I believe strongly that this should be the default expectation for any tool used by the build process that is not installed via tooltool.  It's already the case for tc-vcs, git, Python, Node, etc.
Moving to TaskCluster component...
Component: TaskCluster → Integration
Product: Testing → Taskcluster
Component: Integration → Platform and Services
You need to log in before you can comment on or make changes to this bug.