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

Map a commit sha to an artifact and provenance #33

Closed
behnazh-w opened this issue Jan 24, 2023 · 2 comments
Closed

Map a commit sha to an artifact and provenance #33

behnazh-w opened this issue Jan 24, 2023 · 2 comments
Labels
enhancement Enhancement of a feature slsa-provenance The issues related to SLSA provenances

Comments

@behnazh-w
Copy link
Member

Macaron can analyze a specific <branch, commit sha> of a repo. However, the provenance analyzer looks for the provenance in the latest release. We need to search the releases to match the provided commit sha if possible and analyze the corresponding artifact and provenance. We can add an optional artifact version input to assist the search.

If we cannot find such mapping, we can fall back to analyze the latest release and analyze the repo with its corresponding <branch, commit sha>.

@behnazh-w behnazh-w added improvement enhancement Enhancement of a feature and removed improvement labels Jan 24, 2023
@behnazh-w
Copy link
Member Author

Once we complete this enhancement to map artifacts/provenances to a commit sha, issues like this one would be avoided because we would analyze the artifact corresponding to the specified commit sha in e2e test configurations (and not just the latest release artifact).

@behnazh-w
Copy link
Member Author

This issue can be closed as the commit finder maps the artifact to commits.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Enhancement of a feature slsa-provenance The issues related to SLSA provenances
Projects
None yet
Development

No branches or pull requests

1 participant