8000 Enable Trivy failures in docker action · Issue #118 · celestiaorg/.github · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Enable Trivy failures in docker action #118

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.

Sign up for GitHub 8000

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

Jump to bottom
Closed
MSevey opened this issue Oct 23, 2024 · 2 comments
Closed

Enable Trivy failures in docker action #118

MSevey opened this issue Oct 23, 2024 · 2 comments
Labels
github_actions Pull requests that update GitHub Actions code

Comments

@MSevey
Copy link
Contributor
MSevey commented Oct 23, 2024 •
edited
Loading

Currently the Trivy check only reports errors it doesn't actually cause the pipeline to fail.

### Tasks
- [ ] Enable on devops branch
- [ ] Test on app and node
- [ ] Fix any errors
- [ ] Push to main, add specific call out in the release notes
- [ ] https://github.com/celestiaorg/.github/pull/119
@MSevey MSevey self-assigned this Oct 23, 2024
@MSevey MSevey mentioned this issue Oct 23, 2024
Closed
@MSevey MSevey added github_actions Pull requests that update GitHub Actions code and removed needs: triage labels Oct 23, 2024
@MSevey
Copy link
Contributor Author
MSevey commented Oct 23, 2024

Also remove the VEX warning, REF: https://github.com/celestiaorg/celestia-node/actions/runs/11456093028/job/31873505275

@MSevey MSevey removed their assignment Apr 10, 2025
@smuu
Copy link
Member
smuu commented May 16, 2025

we don't want trivy

@smuu smuu closed this as completed May 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
github_actions Pull requests that update GitHub Actions code
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MSevey @smuu
0