-
-
Notifications
You must be signed in to change notification settings - Fork 249
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
add download and sbom verification scripts #3516
Conversation
Signed-off-by: Stewart X Addison <[email protected]>
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.
A block has been put on this Pull Request as this repository is temporarily under a code freeze due to an ongoing release cycle.
If this pull request needs to be merged during the release cycle then please comment /merge
and a PMC member will be able to remove the block.
If the code freeze is over you can remove this block by commenting /thaw
.
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.
some shellcheck changes required.
/thaw |
Pull Request unblocked - code freeze is over.
69292a5
to
3963038
Compare
a6105fd
to
e37525d
Compare
Signed-off-by: Stewart X Addison <[email protected]>
e37525d
to
569ba0d
Compare
Provides basic IVT testing (Download from the github repos) and validation of GPG and sha checksums as well as some validation of the downloaded SBOM to ensure it meets the CycloneDX requirements and has sane data in it as required to achieve SLSA Level 3 compliance.
This will be run via the jenkins job at https://ci.adoptium.net/job/build-scripts/job/release/job/download_and_sbom_validation - currently restricted access as per other tools in the
release
folder in jenkins.Fixes #3506 (that issue has some follow-on ideas for improvements too)
Also probably implements all of the initial reuqirements of #3484 but there will likely be some additions to check the formal mac/windows signing so I don't want that one closed just yet :-)
Note this is not currently added as a formal step into RELEASING.md but that should be included in the future.