docker-worker: worker types not aligned on docker-worker version
Categories
(Taskcluster :: Workers, enhancement)
Tracking
(Not tracked)
People
(Reporter: pmoore, Unassigned)
References
Details
In investigating bug 1535179 I discovered that we have a range of docker-worker AMIs deployed in production:
ami-ec806794
wcosta-debug
worker-ci-test
ami-17373968
ami-6a5ab709
ami-6d401815
fp-gecko-3-b-linux
ami-44091d24
ami-7a079702
ami-cd5c9fb0
gecko-1-linux-shared
gecko-2-linux-shared
gecko-3-linux-shared
releng-svc-prod
ami-0c474a6c
ami-60d46918
ami-d34268a9
ami-test-pv
ami-5c43f923
ami-84d7a3fc
ami-bd0e11dd
gecko-1-b-linux-gps
ami-0733e29ad332b4345
ami-0a8fce99aa5b3d9e1
ami-0ed64075d35d58fc7
deepspeech-kvm-worker
hg-push
releng-svc-memory
ami-0026287f
ami-a45db0c7
servo-docker-untrusted
servo-docker-worker
ami-04154ad215fdf98f8
ami-072cd000ce46f5e48
ami-0c3a25a55027f6293
mozillaonline-1-b-linux
mozillaonline-3-b-linux
ami-0292e4456a62686b2
ami-04ab5433634023fbd
ami-0b98e3cafbe40adb0
ami-test
ami-010f8632e858089cd
ami-0809dc3185d30c425
ami-0d2e14f2a00a42c94
android-api-15
android-components-g
application-services-r
b2gbuild
b2gtest
balrog
cli
cratertest
dbg-linux32
dbg-linux64
dbg-macosx64
deepspeech-worker
desktop-test
desktop-test-large
desktop-test-xlarge
flame-kk
funsize-balrog
funsize-balrog-dev
funsize-mar-generator
fuzzer
gaia
gaia-cache
gaia-decision
gecko-1-b-android
gecko-1-b-linux
gecko-1-b-linux-large
gecko-1-b-linux-xlarge
gecko-1-b-macosx64
gecko-1-decision
gecko-1-images
gecko-2-b-android
gecko-2-b-linux
gecko-2-b-linux-large
gecko-2-b-linux-xlarge
gecko-2-b-macosx64
gecko-2-decision
gecko-2-images
gecko-misc
gecko-symbol-upload
gecko-t-linux-large
gecko-t-linux-xlarge
github-worker
hg-worker
mobile-1-b-andrcmp
mobile-1-b-fenix
mobile-1-b-ref-browser
mobile-1-decision
mobile-1-images
mulet-debug
mulet-opt
opt-linux32
opt-linux64
opt-macosx64
releng-svc
releng-svc-compute
releng-task
rustbuild
spidermonkey
symbol-upload
taskcluster-generic
tcvcs-cache
tcvcs-cache-device
tutorial
wpt-docker-worker
ami-26170546
ami-3d533e45
ami-90bb1aef
gecko-focus
ami-02a7f804a264b7e7f
ami-0a0232431283656bd
ami-0e1126f4ba28898df
gecko-3-b-android
gecko-3-b-linux
gecko-3-b-linux-large
gecko-3-b-linux-xlarge
gecko-3-b-macosx64
gecko-3-decision
gecko-3-images
gecko-decision
gecko-images
mobile-3-b-andrcmp
mobile-3-b-fenix
mobile-3-b-ref-browser
mobile-3-decision
mobile-3-images
taskcluster-images
ami-6f401817
gecko-1-b-linux-usw2
servo-docker-untrusted
servo-docker-worker
version-control-tools
Comment 1•7 years ago
|
||
(In reply to Pete Moore [:pmoore][:pete] from comment #0)
In investigating bug 1535179 I discovered that we have a range of docker-worker AMIs deployed in production:
I've added some comments on the workers that I have some idea of the state of.
ami-ec806794
wcosta-debug
worker-ci-testami-0c474a6c
ami-60d46918
ami-d34268a9
ami-test-pvami-0292e4456a62686b2
ami-04ab5433634023fbd
ami-0b98e3cafbe40adb0
ami-test
These are all appear to be test worker types, so I'm not surprised at them being on random versions.
We can probably update them to current (non-gecko?) images if they aren't actively being used.
I also wonder if we need both ami-test and ami-test-pv now.
ami-5c43f923
ami-84d7a3fc
ami-bd0e11dd
gecko-1-b-linux-gps
This can be deleted.
ami-010f8632e858089cd
ami-0809dc3185d30c425
ami-0d2e14f2a00a42c94
android-api-15
android-components-g
application-services-r
[...]
These are the untrusted current workers.
ami-02a7f804a264b7e7f
ami-0a0232431283656bd
ami-0e1126f4ba28898df
gecko-3-b-android
[...]
These are the trusted current workers.
| Reporter | ||
Comment 2•6 years ago
|
||
Hi Tom, guessing we can close this now that ci-admin manages worker pools - do you agree?
Updated•6 years ago
|
Description
•