Bugzilla

New GCP / AWS images created for FirefoxCI docker-worker worker pools (with the exception of [gecko-1/masterwayz-bug1764751](https://firefox-ci-tc.services.mozilla.com/worker-manager/gecko-1%2Fmasterwayz-bug1764751) which is being handled in bug 1764751 comment 7.

New GCP / AWS images created for FirefoxCI docker-worker worker pools (with the exception of [gecko-1/masterwayz-bug1764751](https://firefox-ci-tc.services.mozilla.com/worker-manager/gecko-1%2Fmasterwayz-bug1764751) which is being handled in bug 1764751 comment 7).

The above patch will update the production worker pools to use them, on landing.

New GCP / AWS images created for all the FirefoxCI docker-worker worker pools listed in comment 5 (with the exception of [gecko-1/masterwayz-bug1764751](https://firefox-ci-tc.services.mozilla.com/worker-manager/gecko-1%2Fmasterwayz-bug1764751) which is being handled separately in bug 1764751 comment 7).

The above patch will update the production worker pools to use them, on landing.

I have created new GCP / AWS images for all the FirefoxCI docker-worker worker pools listed in comment 5 (with the exception of [gecko-1/masterwayz-bug1764751](https://firefox-ci-tc.services.mozilla.com/worker-manager/gecko-1%2Fmasterwayz-bug1764751) which is being handled separately in bug 1764751 comment 7).

The above patch will update the production worker pools to use them, on landing.

I have created new GCP / AWS images for all the FirefoxCI docker-worker worker pools (with the exception of [gecko-1/masterwayz-bug1764751](https://firefox-ci-tc.services.mozilla.com/worker-manager/gecko-1%2Fmasterwayz-bug1764751) which is being handled separately in bug 1764751 comment 7). See comment 5 for the breakdown by image (set).

The above patch will update the production worker pools to use them, on landing.

I have created new GCP / AWS images for all the FirefoxCI docker-worker worker pools (with the exception of [gecko-1/masterwayz-bug1764751](https://firefox-ci-tc.services.mozilla.com/worker-manager/gecko-1%2Fmasterwayz-bug1764751) which is being handled separately in bug 1764751 comment 7). See comment 5 for the breakdown by image (set).

The above patch will update the production worker pools to use them, on landing.

Note, the new machine images were generated by running [this script](https://github.com/mozilla/community-tc-config/blob/d2b36727db19bba379953d54042a3569a5898368/imagesets/docker-worker/bootstrap.sh) against the old machine images.

I have created new GCP / AWS images for all the FirefoxCI docker-worker worker pools (with the exception of [gecko-1/masterwayz-bug1764751](https://firefox-ci-tc.services.mozilla.com/worker-manager/gecko-1%2Fmasterwayz-bug1764751) which is being handled separately in bug 1764751 comment 7). See comment 5 for the breakdown by image (set).

The above patch will update the production worker pools to use them, on landing.

Note, the new machine images were generated by running [this cert-patching script](https://github.com/mozilla/community-tc-config/blob/d2b36727db19bba379953d54042a3569a5898368/imagesets/docker-worker/bootstrap.sh) against the old machine images.

I have created new GCP / AWS images for all the FirefoxCI docker-worker worker pools (with the exception of [gecko-1/masterwayz-bug1764751](https://firefox-ci-tc.services.mozilla.com/worker-manager/gecko-1%2Fmasterwayz-bug1764751) which is being handled separately in bug 1764751 comment 7). See comment 5 for the breakdown by image (set).

The above patch will update the production worker pools to use them, on landing.

Note, the new machine images were generated by running [this cert-patching script](https://github.com/mozilla/community-tc-config/blob/d2b36727db19bba379953d54042a3569a5898368/imagesets/docker-worker/bootstrap.sh) against the old machine images.

This is the same technique that was used in bug 1714818 a year ago to patch the certificates then, and also the technique used in comment 2 to update Community-TC cluster too, so it should be fairly reliable. I was also able to confirm that none of the images had changed since the previous update.

I have created new GCP / AWS images for all the FirefoxCI docker-worker worker pools (with the exception of [gecko-1/masterwayz-bug1764751](https://firefox-ci-tc.services.mozilla.com/worker-manager/gecko-1%2Fmasterwayz-bug1764751) which is being handled separately in bug 1764751 comment 7). See comment 5 for the breakdown by image (set).

The above patch will update the production worker pools to use them, on landing.

Note, the new machine images were generated by running [this cert-patching script](https://github.com/mozilla/community-tc-config/blob/d2b36727db19bba379953d54042a3569a5898368/imagesets/docker-worker/bootstrap.sh) against the old machine images.

This is the same technique that was used in bug 1714818 a year ago to patch the certificates then, and also the technique used in comment 2 to update Community-TC cluster too, so it should be fairly reliable. I was also able to confirm that none of the machine images had changed since the previous update in bug 1714818.

I have created new GCP / AWS images for all the FirefoxCI docker-worker worker pools (with the exception of [gecko-1/masterwayz-bug1764751](https://firefox-ci-tc.services.mozilla.com/worker-manager/gecko-1%2Fmasterwayz-bug1764751) which is being handled separately in bug 1764751 comment 7). See comment 5 for the breakdown by image (set).

The above patch will update the production worker pools to use them, on landing.

Note, the new machine images were generated by running [this cert-patching script](https://github.com/mozilla/community-tc-config/blob/d2b36727db19bba379953d54042a3569a5898368/imagesets/docker-worker/bootstrap.sh) against the old machine images.

This is the same technique that was used in bug 1714818 in October to patch the certificates then, and also the technique used in comment 2 to update Community-TC cluster too, so it should be fairly reliable. I was also able to confirm that none of the machine images had changed since the previous update in bug 1714818.