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.

Sign up for GitHub

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

Add where next section #2

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add where next section #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -298,3 +298,10 @@ image running. The image tag should be the short-sha of your new HEAD commit
- There is an attestation called `alpha.unit-test`
- Click the `>` chevron in the Trail to open the attestation drop-down
- Browse the JUnit results in the JSON sent by the `kosli attest junit` command

## Where next?

Congratulations, you've successfully instrumented a pipeline to record evidence for a software delivery process! Here's a few things that you can try now to learn some more:

- Can you make a [generic attestation](https://docs.kosli.com/client_reference/kosli_attest_generic/) to record the lint step in the pipeline?
- Unlike the junit attestation, the Kosli CLI can't determine whether the linting is compliant, how can you record a non-compliant attestation if the linting fails?