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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Multiple pipelines from the same commit, deployment help Edited

I have a single repo which contains multiple build targets/variants, and I'm working on the release/deployment process for the images right now. I want to allow manual triggering of deployments for each image, from each commit to master. Each one needs to separately go through test, staging, and production deployment environments. The problem is that each manual step requires all previous steps in the pipeline to pass,, which means a pipeline like this doesn't work:

- step: *build-target-a

- step: *build-target-b

- step: *deploy-a-test

- step: *deploy-b-test

- step: *deploy-a-staging

- step: *deploy-b-staging

- step: *deploy-a-production

- step: *deploy-b-production

This won't work because all the deploy steps are manually triggered, and i can't deploy-b-staging until I run deploy-a-test. This gets worse as I go down the chain - e.g. I can't deploy-b-production until I deploy-a-production, when I might not want to deploy-a-production at all.

So, I tried splitting them into separate pipelines (sorry for formatting):

pipelines:

 branches:

  master:

   - step: *build-target-a

   - step: *deploy-a-test

   - step: *deploy-a-staging

   - step: *deploy-a-production

  master:

   - step: *build-target-b

   ...

But, this configuration is invalid because the 'master' key is repeated twice.

I also know that you can't trigger manual steps in parallel - not that that would've really helped here anyway.

I COULD make a custom deploy step where you go to the commit, and run the "deploy-target-a" pipeline. But, I want to use the BITBUCKET_BUILD_NUMBER as part of my build. I might end up with out of order build numbers if i do this - e.g. if I ran "deploy-target-a" on the latest commit, then I went back to a previous commit and ran "deploy-target-a", the later commit would have an earlier build number.

My question is: what do you think is a working or good solution, or is there even one out there?

1 answer

0 votes

Hi @MichaelHobo

It looks like you'd want to trigger multiple pipelines for a push, that is currently not supported even though you could hack your yml in a such a way that the same branch would match multiple times like `master` `maste*` `mast*` etc. I would suggest raising a feature request describing your use case in https://jira.atlassian.com/projects/BCLOUD/issues/

As for parallel steps with manual triggers there is a ticket https://jira.atlassian.com/browse/BCLOUD-16650 that you may want to vote or watch for updates.

Thanks,
Peter

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bitbucket

Calling any interview participants for Bitbucket Data Center

Hi everyone,  We are looking to learn more about development teams’ workflows and pain points, especially around DevOps, integrations, administration, scale, security, and the related challeng...

442 views 4 4
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you