It should be trivial to see packer config for how an ami was created
Categories
(Taskcluster :: Workers, defect)
Tracking
(Not tracked)
People
(Reporter: pmoore, Unassigned)
References
(Depends on 1 open bug)
Details
Reporter | ||
Updated•10 years ago
|
Updated•8 years ago
|
Comment 1•7 years ago
|
||
Reporter | ||
Comment 2•7 years ago
|
||
Reporter | ||
Updated•7 years ago
|
Comment 3•7 years ago
|
||
Comment 4•7 years ago
|
||
Assignee | ||
Updated•6 years ago
|
Reporter | ||
Comment 5•6 years ago
|
||
This is solved by the generic-worker to docker-worker migration, since generic-worker tasks link to a source file which describes how the host machine was set up.
Comment 6•5 years ago
|
||
Pete, there might be some good ideas here to mix into discussions of how we recommend users handle image generation..
Reporter | ||
Comment 7•5 years ago
•
|
||
We could make the workers (generic-worker/docker-worker) have a required config property, which is a link to the host environment definition, which gets reported in the task log header of all task runs they execute.
Currently the capability to provide the link to the host environment exists in generic-worker, but it isn't enforced.
I don't think such a feature exists in docker-worker.
I have mixed feelings about whether it should be enforced or not by the worker, but I strongly feel for worker types that we manage on the community cluster, we should provide this information, and that docker-worker should also support the feature. I think it is reasonable to expect this of the firefox cluster too.
Reporter | ||
Comment 8•4 years ago
|
||
Not actively working on this at the moment.
Reporter | ||
Comment 9•2 years ago
|
||
Reopening inactive bugs, because they may still need attention. Historically, inactive bugs were closed, but this hides the fact there are genuine issues which have not been resolved.
Reporter | ||
Updated•2 years ago
|
Description
•