Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

switch windows builds to use docker image from azurecr #1170

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

sxa
Copy link
Member

@sxa sxa commented Dec 19, 2024

Currently the windows container builds are using a local container image on the machine which is not scalable and takes a while to update. This change will pull from the private azure container registry with a credential where we are storing the container images.

Partially fixes adoptium/infrastructure#3217 (For Windows only)
Related adoptium/infrastructure#3780 which is required to keep the image up to date with the playbooks

Related: The docker file used for creating this image is https://github.com/adoptium/infrastructure/blob/master/ansible/docker/Dockerfile.win2022

Also for reviewers: I'd much rather rename this credential prior to making this live since it might get mistaken for an actual credential (It's not - it's the ID/label in our jenkins instance of the stored credential)

Also FYI @AdamBrousseau for awareness. This is likely the final step in making our Windows Temurin builds run as well as they can in containers, and make it consistent with the Linux builds.

Copy link

Thank you for creating a pull request!

Please check out the information below if you have not made a pull request here before (or if you need a reminder how things work).

Code Quality and Contributing Guidelines

If you have not done so already, please familiarise yourself with our Contributing Guidelines and Code Of Conduct, even if you have contributed before.

Tests

Github actions will run a set of jobs against your PR that will lint and unit test your changes. Keep an eye out for the results from these on the latest commit you submitted. For more information, please see our testing documentation.

In order to run the advanced pipeline tests (executing a set of mock pipelines), it requires an admin to post run tests on this PR.
If you are not an admin, please ask for one's attention in #infrastructure on Slack or ping one here.
To run full set of tests, use "run tests"; a subset of tests on specific jdk version, use "run tests quick 11,21"

@sxa
Copy link
Member Author

sxa commented Dec 19, 2024

It doesn't look like we're going to have any EA builds tonight (no new tags) so I'll kick off a full set of tests to verify that the regeneration works ok with these parameters which haven't been used in our CI previously.

@sxa
Copy link
Member Author

sxa commented Dec 19, 2024

run tests

@eclipse-temurin-bot
Copy link
Collaborator

 PR TESTER RESULT 

❎ Some pipelines failed or the job was aborted! ❎
See the pipeline-build-check below for more information...

@sxa
Copy link
Member Author

sxa commented Dec 19, 2024

Shame on both reviewers for not spotting the typo ;-) windows2022_build_iamge instead of windows2022_build_image. Take 2!

@sxa
Copy link
Member Author

sxa commented Dec 19, 2024

run tests

@sxa
Copy link
Member Author

sxa commented Dec 19, 2024

@eclipse-temurin-bot
Copy link
Collaborator

 PR TESTER RESULT 

❎ Some pipelines failed or the job was aborted! ❎
See the pipeline-build-check below for more information...

@sxa
Copy link
Member Author

sxa commented Dec 19, 2024

Latest set of tests seemed to still be trying to pull adoptium.azurecr.io/windows2022_build_iamge for some reason despite this PR having been updated to correct that so I'll try again

@sxa
Copy link
Member Author

sxa commented Dec 19, 2024

run tests

@eclipse-temurin-bot
Copy link
Collaborator

 PR TESTER RESULT 

✅ All pipelines passed! ✅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

Successfully merging this pull request may close these issues.

Identify suitable off-machine location for storing private build container images
4 participants