fix(pipelineGraph): Handling exception when requisiteStageRefIds is not defined (backport #10086) #10087
+3
−0
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
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
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.
Deck prior to 1.27.x was rendering the pipelines when the first stages didnt have defined the requisiteStageRefIds.
Although this was not ideal it allowed users to template their first stages without the key. After the pipelineGraph updates this is causing an exception and breaking the rendering of the pipelines causing issues to users upgrading.
With this fix it is checked if the key is not defined and defaulting it to a empty array.
This is an automatic backport of pull request #10086 done by [Mergify](https://mergify.com).