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

Identify suitable off-machine location for storing private build container images #3217

Open
sxa opened this issue Oct 17, 2023 · 5 comments · May be fixed by adoptium/ci-jenkins-pipelines#1170

Comments

@sxa
Copy link
Member

sxa commented Oct 17, 2023

Due to licensing issues we cannot ship the RHEL/s390x build image to the public so it will need to be in a private location. This issue covers identifying somewhere suitable.

Follow-up to #2731

Noting also that at present the images are not being automatically regenerated when the playbooks are updated, which could be a first step that can be done before pushing it externally.

@sxa
Copy link
Member Author

sxa commented Dec 1, 2023

Related: #3182

@sxa
Copy link
Member Author

sxa commented Aug 14, 2024

This is also relevant for the newly tested docker images for Windows which will also need to be in a private repository so they can be shared:

Options:

Noting that the OpenJ9 team use a private repository so that is known to work well.

@sxa sxa changed the title Identify suitable off-machine location for storing Linux/s390x build images Identify suitable off-machine location for storing private build container images Aug 14, 2024
@sxa sxa added the os:windows label Oct 15, 2024
@sxa
Copy link
Member Author

sxa commented Oct 15, 2024

@gdams Since you're more likely to be familiar with it (and I understand from earlier discussions this might be outside our sponsored credits) can you look at what we need to get us set up with ACR for Windows (and probably s390x for now) build docker images?

@gdams
Copy link
Member

gdams commented Oct 15, 2024

I had an old container registry setup a while ago (adoptium.azurecr.io). There's a few steps to getting it running in a GH actions env

@sxa
Copy link
Member Author

sxa commented Dec 16, 2024

@gdams Where are we with this at the moment? Are we set up with appropriate credentials to be able to pull from the Azure registry during the builds?

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

Successfully merging a pull request may close this issue.

2 participants