[8.14](backport #39533) [BK] - Remove certain steps from running for Branches#39550
Merged
alexsapran merged 1 commit into8.14from May 14, 2024
Merged
[8.14](backport #39533) [BK] - Remove certain steps from running for Branches#39550alexsapran merged 1 commit into8.14from
alexsapran merged 1 commit into8.14from
Conversation
This commit makes some adjustments in the step conditions after reviewing the Jenkins files and how we perform the step validations in Jenkinsfile. If there is a key `when` inside the Jenkinsfile step, it will validate the required conditions, and if there are no `branches: true`, then it will not include that step. Signed-off-by: Alexandros Sapranidis <alexandros@elastic.co> (cherry picked from commit 176e9b8)
alexsapran
approved these changes
May 14, 2024
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Proposed commit message
This commit makes some adjustments in the step conditions after reviewing the Jenkins files and how we perform the step validations in Jenkinsfile.
If a key
whenis inside the Jenkinsfile step 1, it will validate the required conditions 2, and if there are nobranches: true, it will not include that step.I tried to go over the various project and try to consolidate the conditions.
This is an automatic backport of pull request #39533 done by Mergify.