docs: Add Dagger integration section and cleanup Ecosystem CICD docs page #5608
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
Signed-off-by: Jeremy Adams <jeremy@dagger.io>
Signed-off-by: Jeremy Adams <jeremy@dagger.io>
Signed-off-by: Jeremy Adams <jeremy@dagger.io>
|
|
jpadams
changed the title
itaysk
approved these changes
Nov 17, 2023
jpadams
changed the title
|
@itaysk Thank you for the merge! Not sure what needs to happen for this content to go live at https://aquasecurity.github.io/trivy/latest/ecosystem/cicd/. Maybe a manual deploy of your static site? Not sure if I need to do something to trigger that. |
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.
Description
Adds a Dagger integration section and cleans up a couple of minor things on the Ecosystem CICD docs page.
There is a Dagger integration for Trivy that we want to share through the docs page, so I made an update. In the course of updating the page, I noticed that the Azure DevOps content was stuck in the middle of the GitHub Actions content, so I moved that out to stand alone. I also noticed that integrations were using H2 (##) markdown, but the Buildkite entry was using H3 (###), so I fixed that to make things consistent.
Related issues
Related PRs
Remove this section if you don't have related PRs.
Checklist
I've added tests that prove my fix is effective or that my feature works.I've added usage information (if the PR introduces new options)I've included a "before" and "after" example to the description (if the PR is a user interface change).