The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Can we maintain CI/CD script and source conde separate repo.

Jayaram32
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 6, 2024

Hi Team ,

My self Jayaram. 

Can we maintain src code and CI/CD code in separate branches.

While triggering pipeline manually  it should show all branches listed in to the dropdown and we should be able to select which branch I want to trigger.

is this possible in Bitbcuket. 

If i am mentioning like below :
branches:

      develop;

If am mentioning like this , I can see in dropdown only develop. If i mentioned all names. all branches will trigger. 

 

How can i achieve this in bitbucket. 

 

Thanks & Regards,

Jaya Ramarao S.

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Mark C
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 8, 2024

Hi @Jayaram32,

Welcome to the community.

That is indeed possible using branches.
What you would need to do is to ensure you don't have the file "bitbucket-pipelines.yml" in your desired branch so that it won't trigger builds in that branch.
Otherwise, what you can do is to separate it between two repositories. Like one repository for source code, and the other is for Bitbucket Cloud Pipelines. You can then use the trigger-pipeline pipes to trigger builds from one repository to another.

Regards,
Mark C

DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Product Admin Site Admin
TAGS
AUG Leaders

Atlassian Community Events