-
-
Notifications
You must be signed in to change notification settings - Fork 71
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
Do not issue docker pull if imagename contains rhel #611
Conversation
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 GuidelinesIf you have not done so already, please familiarise yourself with our Contributing Guidelines and Code Of Conduct, even if you have contributed before. TestsGithub 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 |
PR TESTER RESULT ✅ All pipelines passed! ✅ |
This didn't work https://ci.adoptopenjdk.net/job/build-scripts-pr-tester/job/build-test/job/jobs/job/jdk17u/job/jdk17u-linux-x64-temurin/109/console (Note that that job was run with labels for EDIT: That issue has now been fixed but it still isn't running through the tests correctly: https://ci.adoptopenjdk.net/job/build-scripts-pr-tester/job/build-test/job/jobs/job/jdk17u/job/jdk17u-linux-x64-temurin/113/console |
Signed-off-by: Stewart X Addison <sxa@redhat.com>
run tests |
PR TESTER RESULT ❎ Some pipelines failed or the job was aborted! ❎ |
Taking out of draft now that the UID problem referred to in adoptium/infrastructure#2731 (comment) - adoptium/infrastructure#2982 now creates the jenkins user with the UID expected on our Marist s390x systems and can complete builds. |
@andrew-m-leonard How can I re-run the failing check? Just doing a straight rebuild of the jenkins job doesn't seem to work |
This looks like it might be a failure in the SBOM generation on macos: https://ci.adoptium.net/job/build-scripts-pr-tester/job/build-test/job/jobs/job/jdk17u/job/jdk17u-mac-x64-temurin/96/console
(Annoyingly it's quite non-obvious from the check job which bit is failing as they all show as green in the blue ocean view) |
That's weird, is that SBOM failure repeatable? If you re-run the github CI build pipeline task? |
What do you mean by As per earlier comment I can't just click rebuild on the job in jenkins :-( |
run tests |
Yeah sorry meant "run tests" for this one |
PR TESTER RESULT ❎ Some pipelines failed or the job was aborted! ❎ |
👍🏻 xlinux failed this time but that's a known issue which has now been resolved so I'll re-trigger |
run tests |
PR TESTER RESULT ✅ All pipelines passed! ✅ |
1 similar comment
PR TESTER RESULT ✅ All pipelines passed! ✅ |
Noting that we already pull with credential, why don’t you just push to dockerhub and mark it as private? Seems less prone to errors and requires no additional code changes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Frustrating that this PR was merged without a response to my query, this seems like a completely unnecessary code change to solve a problem that doesn't exist. |
Apologies for missing your comment on this occasion. Feel free to submit a follow-on in order to change the mechanism. |
Signed-off-by: Stewart X Addison <sxa@redhat.com>
Signed-off-by: Stewart X Addison <sxa@redhat.com>
rhel images cannot be uploaded to dockerhub, so this is a test to see if we can use a local image on the machine. A final solution is likely to involve pushing it into a credentials-protected location, or having an additional parameter to skip the pull operation but that can be done as a subsequent step.
Signed-off-by: Stewart X Addison sxa@redhat.com