Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Initiating pipelines on branch other than master

I had to add pipelines to a number of older projects which hold master with different level of regard. That is, some projects have a convention for what goes into master and who does it. 

I'd like to create a branch for the sole purpose of adding a pipeline config etc.

However there does not appear to be a way to initialize pipelines by committing a config file (standard name) to any other branch than master.

Am I wrong about that as I hope I am?  I have always worked around, but... that's the questions


1 answer

0 votes
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jun 17, 2020

Actually it should be possible on any branch or revision. Perhaps it depends how the pipeline is executed / triggered.

E.g. IIRC on a topic branch with pipeline changes, default pipeline works (as well a branch pipeline if the topic matches it) and also on the level of the commit all custom pipelines, within a pull request the changed pull-request pipeline.

If you could add a bit more context what you're doing and where the key-point is it does not work for you any longer (and what you would have expected/wanted instead) it should be easier to find out more.

But you have a pipeline in master, what if you don't? I have a pipeline in a branch different to master and not in master and it doesn't seem to give my access to run it.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events