Ability to select a non-master version of a git sync'd chained pipeline from a parent pipeline
long-term
A
Aegean blue Shrimp
Currently we need to consider the following points for executing remote chained pipelines:
A chained pipeline is fetched from the default branch when the parent pipeline is defined inline, and the chained pipeline is defined remotely.
When the parent pipeline is defined remotely, and the chained pipeline is defined inline, the parent pipeline is fetched from the corresponding branch, and the chained pipeline is fetched inline.
When both the chained pipeline and the parent pipeline are defined remotely, but under the same repository, the chained pipeline should belong to the same branch as the parent pipeline.
A chained pipeline is fetched from the default branch when both the parent and chained pipelines are defined remotely in separate repositories. This is irrespective of the branch of the parent pipeline.
Log In
Canny AI
Merged in a post:
FR- Provide a way to load pipeline from respective branch just like template
H
Handsome Camel
Needed an option enabled for pipeline to select from respective branch its is having in the yaml just like template we are having. Because we are always seeing error page saying pipeline not found at opening of the pipeline if the branch does not exists.
Canny AI
Merged in a post:
When a trigger executes a pipeline backed in git we should honor the pipelines specified branch not the branch that simulates the trigger
C
Cerulean Flamingo
Load harness configurations from a specific branch, regardless of which branch is launched in the trigger.
Canny AI
Merged in a post:
Couldn't run pipeline because file doesn't found on master
O
Olive Canid
I create pipeline using the import from git and set the git branch to not master branch but i couldn't to run my pipeline because the pipeline file not found in master branch.
i think we should update the condition to check from master branch and check it from the git branch that we set it.
Canny AI
Merged in a post:
Branch selection for child pipeline in pipeline chaining
I
Inkwell Kite
Currently when a new pipeline stage is added in a parent pipeline the child pipeline defaults to master branch. Please add a functionality to select the branch for child pipeline for pipeline stage. Not every change can be committed to master. Some output variables needed by the parent pipeline might only be available in a branch of the child pipeline. And the functionality is pretty useful for testing the parent and child pipeline.
Canny AI
Merged in a post:
Support Feature Branch to use as part of the Chained pipeline.
R
Regulatory Kite
As of today limitations is When both the chained pipeline and the parent pipeline are defined remotely, but under the same repository, the chained pipeline should belong to the same branch as the parent pipeline.
A chained pipeline is fetched from the default branch when both the parent and chained pipelines are defined remotely in separate repositories. This is irrespective of the branch of the parent pipeline.
Ask is to support this feature when they are present in other branches
Sudarshan Purohit
Regulatory Kite : Thank you for your feature request. At this time, we are unable to support this feature due to the way in which we store the details of the chained remote pipeline in the Harness system. The flow is very similar to how templates stored remotely are used today.
In future, if the system changes, we may be able to support this flow. If possible, could you elaborate on why this use case is important to you, so we can consider it when updating the roadmap?
Thanks,
Sudarshan
CC Prasad Satam
Rohan Gupta
long-term
A
Aegean blue Shrimp
The original post that Harness Support created in this portal is lacking a key sentence from the originating Support Request:
"Can we remove this default branch restriction for chained pipelines like it is being removed for git synced template, which was originally requested on the ticket https://support.harness.io/hc/en-us/requests/38269?"
A
Aegean blue Shrimp
As per our prior conversations with Continuous Seahorse and Familiar Leopard Harness Support has a bad habit of creating enhancement requests in this portal off the back of Support Requests in the other portal, without providing the necessary context in this portal.
A
Aegean blue Shrimp
Prasad Satam Did you review the Support Request which triggered Harness Support to raise this enhancement request?
Load More
→