-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
don't skip docker SHA collection on RHEL containers #1023
Conversation
Signed-off-by: Stewart X Addison <sxa@redhat.com>
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 |
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
PR TESTER RESULT ❎ Some pipelines failed or the job was aborted! ❎ |
pipeline-build-check failure seems to have been this: |
Yup, the workspace.../temp directory had an invalid security setting, and couldn't be deleted, it had to be forced away. This occurred again during the recent release, but I haven't had time to have another look, and currently I cant get on to the box to investigate further. I think, that the folder is being created or modified under cygwin, and something is going awry with the ownership. |
Marked offline for now. |
@sxa remind me how to restart the pipeline-build-check? |
run tests |
It's triggered by a "run tests" comment from an authorised user like the one above (I expect you're authorised!) - it's not mandatory or run by default. |
PR TESTER RESULT ✅ All pipelines passed! ✅ |
Fixes adoptium/temurin-build#3786 #1022
While we don't pull the container build image from an external location on RHEL/s390x, we should still collect the SHA for inclusion in the SBoM.
(Note: It gets into the SBoM via the
-e
parameter passed in from the pipeline when the container is started which setsBUILDIMAGESHA
which is then stored inmetadata/docker.txt
bysbin/prepareWorkspace.sh
which is read bysbin/build.sh
, intobuildimagesha
which is then added to the SBoM bysbin/build.sh
)