Run snyk check in periodic build for each development branch #133751
Merged
Conversation
This file contains hidden or 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
we filter by regex for common name pattern of the dev branches to reduce risk of running from development branch. in reality those periodic builds are not likely to be triggered by developers so this is a good enough compromise. Branches that are not developed anymore will stay in snyk for now and require manual removal.
breskeby
added
>non-issue
:Delivery/Build
|
Pinging @elastic/es-delivery (Team:Delivery) |
breskeby
added a commit
to breskeby/elasticsearch
that referenced
this pull request
Aug 28, 2025
…#133751) we filter by regex for common name pattern of the dev branches to reduce risk of running from development branch. in reality those periodic builds are not likely to be triggered by developers so this is a good enough compromise. Branches that are not developed anymore will stay in snyk for now and require manual removal.
breskeby
added a commit
to breskeby/elasticsearch
that referenced
this pull request
Aug 28, 2025
…#133751) we filter by regex for common name pattern of the dev branches to reduce risk of running from development branch. in reality those periodic builds are not likely to be triggered by developers so this is a good enough compromise. Branches that are not developed anymore will stay in snyk for now and require manual removal.
breskeby
added a commit
to breskeby/elasticsearch
that referenced
this pull request
Aug 28, 2025
…#133751) we filter by regex for common name pattern of the dev branches to reduce risk of running from development branch. in reality those periodic builds are not likely to be triggered by developers so this is a good enough compromise. Branches that are not developed anymore will stay in snyk for now and require manual removal.
breskeby
added a commit
to breskeby/elasticsearch
that referenced
this pull request
Aug 28, 2025
…#133751) we filter by regex for common name pattern of the dev branches to reduce risk of running from development branch. in reality those periodic builds are not likely to be triggered by developers so this is a good enough compromise. Branches that are not developed anymore will stay in snyk for now and require manual removal.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Aug 28, 2025
#133756) we filter by regex for common name pattern of the dev branches to reduce risk of running from development branch. in reality those periodic builds are not likely to be triggered by developers so this is a good enough compromise. Branches that are not developed anymore will stay in snyk for now and require manual removal.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Aug 28, 2025
#133757) we filter by regex for common name pattern of the dev branches to reduce risk of running from development branch. in reality those periodic builds are not likely to be triggered by developers so this is a good enough compromise. Branches that are not developed anymore will stay in snyk for now and require manual removal.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Aug 28, 2025
#133754) we filter by regex for common name pattern of the dev branches to reduce risk of running from development branch. in reality those periodic builds are not likely to be triggered by developers so this is a good enough compromise. Branches that are not developed anymore will stay in snyk for now and require manual removal.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Aug 28, 2025
#133755) we filter by regex for common name pattern of the dev branches to reduce risk of running from development branch. in reality those periodic builds are not likely to be triggered by developers so this is a good enough compromise. Branches that are not developed anymore will stay in snyk for now and require manual removal.
JeremyDahlgren
pushed a commit
to JeremyDahlgren/elasticsearch
that referenced
this pull request
Aug 29, 2025
…#133751) we filter by regex for common name pattern of the dev branches to reduce risk of running from development branch. in reality those periodic builds are not likely to be triggered by developers so this is a good enough compromise. Branches that are not developed anymore will stay in snyk for now and require manual removal.
sarog
pushed a commit
to portsbuild/elasticsearch
that referenced
this pull request
Sep 11, 2025
…#133751) (elastic#133757) we filter by regex for common name pattern of the dev branches to reduce risk of running from development branch. in reality those periodic builds are not likely to be triggered by developers so this is a good enough compromise. Branches that are not developed anymore will stay in snyk for now and require manual removal.
sarog
pushed a commit
to portsbuild/elasticsearch
that referenced
this pull request
Sep 19, 2025
…#133751) (elastic#133757) we filter by regex for common name pattern of the dev branches to reduce risk of running from development branch. in reality those periodic builds are not likely to be triggered by developers so this is a good enough compromise. Branches that are not developed anymore will stay in snyk for now and require manual removal.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
we filter by regex for common name pattern of the dev branches to reduce
risk of running from development branch. in reality those periodic builds are
not likely to be triggered by developers so this is a good enough compromise.
Branches that are not developed anymore will stay in snyk for now and require
manual removal.