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

ci: replace trivy with trivy-action #1871

Merged
merged 2 commits into from
Oct 16, 2024

Conversation

binbin-li
Copy link
Collaborator

@binbin-li binbin-li commented Oct 15, 2024

Description

What this PR does / why we need it:

  1. Switch to trivy-action from trivy CLI to use DB cache for free.
  2. The latest trivy-action will invoke trivy CLI of v0.56.1, and the current trivy CLI that Ratify downloads is v0.46.0
  3. This change will not completely avoid 429 as it's throttling from server side. My test shows the first batch of fetching could be throttled as well, but it can be mitigated a lot for following downloading.

Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):

Fixes github action part for #1866

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Helm Chart Change (any edit/addition/update that is necessary for changes merged to the main branch)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration

  • Test A
  • Test B

Checklist:

  • Does the affected code have corresponding tests?
  • Are the changes documented, not just with inline documentation, but also with conceptual documentation such as an overview of a new feature, or task-based documentation like a tutorial? Consider if this change should be announced on your project blog.
  • Does this introduce breaking changes that would require an announcement or bumping the major version?
  • Do all new files have appropriate license header?

Post Merge Requirements

  • MAINTAINERS: manually trigger the "Publish Package" workflow after merging any PR that indicates Helm Chart Change

Copy link

codecov bot commented Oct 15, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

@binbin-li binbin-li enabled auto-merge (squash) October 16, 2024 04:57
@binbin-li binbin-li disabled auto-merge October 16, 2024 04:57
@binbin-li binbin-li enabled auto-merge (squash) October 16, 2024 04:58
Copy link
Collaborator

@junczhu junczhu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@binbin-li binbin-li merged commit 6376762 into ratify-project:dev Oct 16, 2024
20 checks passed
duffney pushed a commit to duffney/ratify that referenced this pull request Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants