tooling: kicking off setec tooling #33967
Closed
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: Alyssa Wilk <[email protected]>
alyssawilk
commented
May 6, 2024
| - cron: '0 5 * * 1,2,3,4,5' | ||
|
|
||
| permissions: | ||
| contents: read # to fetch code (actions/checkout) |
There was a problem hiding this comment.
not sure if there's any way for this to "run" off envoyproxy/envoy but look at setec (I assume no, which means updates will be annoying but I'm starting with that anyway just to see
There was a problem hiding this comment.
ci cant run in envoy using setec without giving it permissions to do so, which apart from weakening the security there would add a lot of complexity
the easier option is what i suggested elsewhere - strip setec's main to just ci and just add any necessary ci there
Signed-off-by: Alyssa Wilk <[email protected]>
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.
Right now (assuming we have permissions right which I likely don't) this will
in the long run I'm hoping it can do much of the "where are we for release tracking" figuring out which cve-next issues have fixes in progress, approved, etc but starting off simple.