Add a Default Branch option for Pipeline Stages
under review
E
Environmental Parrot
Pipeline Stages do not have a default branch setting like other GitEx entities. This causes issues with IDP if the branch is not explicitly defined and the branch is coming back as null.
Log In
Himanshu Mishra
Hi Shalom! Can you please provide more details of your setup? Are you saying this happens when you trigger a GitEx enabled pipeline from an IDP workflow?
Feel free to share some URLs/screenshots so that we can understand better. Thanks!
E
Environmental Parrot
Himanshu Mishra - Hi. So this is related to a support case we have/had open with harness - https://support.harness.io/hc/en-us/requests/86546
Basically, if you have an IDP workflow that triggers a backend CD pipeline which in turn calls another pipeline through a pipeline stage - you must ensure that the branches align all the way through when the last pipeline is held in "git experience". If the eventual pipeline branch changes - then the IDP workflow is broken.
The problem arises for us as a platform team needing to change the branch around a pipeline that one our customers use - when the pipelines are INLINE there is no need for the IDP workflow to be aware of the eventual pipeline's branch and all works as expected. However, if when the pipelines are REMOTE, a change in the branch breaks the IDP workflow as it no longer knows which branch is used.
Adding the ability for a pipeline stage to specify the branch of the pipeline it calls would help keep the IDP workflow invariant. But perhaps also having the IDP workflows only care about the branch of the immediate pipeline it triggers is needed.
E
Environmental Parrot
Screenshots and explication also in the support case - https://support.harness.io/hc/en-us/requests/86546
Himanshu Mishra
Environmental Parrot: Thank you so much for providing the details! cc Prasad Satam
Shylaja Sundararajan
under review