generated from oracle/template-repo
-
Notifications
You must be signed in to change notification settings - Fork 23
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
feat: add a new check to map artifacts to pipelines #471
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
oracle-contributor-agreement
bot
added
the
OCA Verified
All contributors have signed the Oracle Contributor Agreement.
label
Sep 12, 2023
behnazh-w
changed the title
Add artifact match pipeline check
feat: add a new check to map artifacts to pipelines
Sep 12, 2023
behnazh-w
force-pushed
the
add-artifact-match-pipeline-check
branch
2 times, most recently
from
September 12, 2023 12:59
f6128e4
to
7cc62b6
Compare
Signed-off-by: behnazh-w <[email protected]>
behnazh-w
force-pushed
the
add-artifact-match-pipeline-check
branch
from
September 13, 2023 00:06
b36f0ff
to
9d628de
Compare
Signed-off-by: behnazh-w <[email protected]>
behnazh-w
force-pushed
the
add-artifact-match-pipeline-check
branch
from
September 13, 2023 00:40
9d628de
to
5cfd17a
Compare
tromai
reviewed
Sep 13, 2023
src/macaron/slsa_analyzer/package_registry/maven_central_registry.py
Outdated
Show resolved
Hide resolved
tromai
reviewed
Sep 13, 2023
tromai
reviewed
Sep 13, 2023
tromai
reviewed
Sep 13, 2023
tromai
reviewed
Sep 13, 2023
Signed-off-by: behnazh-w <[email protected]>
Signed-off-by: behnazh-w <[email protected]>
tromai
reviewed
Sep 13, 2023
tromai
reviewed
Sep 13, 2023
Signed-off-by: behnazh-w <[email protected]>
Signed-off-by: behnazh-w <[email protected]>
tromai
approved these changes
Sep 13, 2023
art1f1c3R
pushed a commit
that referenced
this pull request
Nov 29, 2024
This PR adds a new check, `mcn_infer_artifact_pipeline_1` to detect a potential pipeline from which an artifact is published. When a verifiable provenance is found for an artifact, the result of this check can be discarded. Otherwise, we check whether a CI workflow run has automatically published the artifact. This check supports Maven artifacts built using Gradle or Maven and published on Maven Central only. Support for other registries and ecosystems will be added in the future. Signed-off-by: behnazh-w <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a new check,
mcn_infer_artifact_pipeline_1
to detect a potential pipeline from which an artifact is published.When a verifiable provenance is found for an artifact, the result of this check can be discarded. Otherwise, we check whether a CI workflow run has automatically published the artifact.
We use several heuristics in this check:
This check supports Maven artifacts built using Gradle or Maven and published on Maven Central only. Support for other registries and ecosystems will be added in the future.
Note: due to a limitation, we cannot specify the provenance checks as parents of this check because a check cannot have more than one parent in the current design. It would be good to skip this with a success result if the relevant provenance checks pass in the future.