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

Test #17

Closed
wants to merge 3 commits into from
Closed

Test #17

wants to merge 3 commits into from

Conversation

rparrett
Copy link
Owner

@rparrett rparrett commented Feb 21, 2024

Test comparing to merge base when doing cargo deny checks

@rparrett rparrett force-pushed the cargo-deny-test branch 10 times, most recently from 73d4d9d to afefc4d Compare February 21, 2024 21:55
run: cargo update
- name: Check for banned and duplicated dependencies (PR)
run: |
#!/bin/bash

Choose a reason for hiding this comment

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

this shouldn't be needed

Copy link
Owner Author

Choose a reason for hiding this comment

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

oops, artifact of local testing

- name: Check for banned and duplicated dependencies (base)
run: |
set -o history
OUT_FILE=/tmp/deny-bans-base

Choose a reason for hiding this comment

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

could you put the two OUT_FILE vars in an env: at the start of the job with different names?

@rparrett
Copy link
Owner Author

I really wanted to find a convenient way to avoid repeating

cargo deny --format json check bans 2>&1 | jq -r -n '[inputs][] | select(.fields.severity != null) | "\(.fields.severity) \(.fields.message)"'

without getting into a nightmare of escaping quotes and stuff but ultimately failed

@mockersf
Copy link

I think you could have a "tooling" step in the job that would output the jq filter to a script, and reuse it in both steps

@rparrett rparrett closed this Aug 12, 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.

2 participants