Downstream pipeline

[salway]

Can a pipeline, after a stage has completed successfully, start another pipeline?

[Jeroen De Raedt]

What exactly are you trying to accomplish? 

With pipelines you have multiple sequential steps within the same pipeline (see https://blog.bitbucket.org/2017/10/03/multiple-steps-in-bitbucket-pipelines/). 

Alternatively, you can use our REST API to kick off a new pipeline as part of your step script: https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/%7Busername%7D/%7Brepo_slug%7D/pipelines/#post

[salway]

Actually, after trying BitBucket Pipelines, we realised that we needed a few more things before moving away from Jenkins and in fact are looking at moving to GoCD.

Requirements:

1. The ability to use common build scripts - we have over 100 similar modules that all build independently but with the same build process.  Jenkins and GoCD allows us to centralise the build commands so we can change all 100 tools build process in one place.  Where GoCD lacks though is that you can't add custom scripts to a pipeline (once you've chosen to use a template, you are fixed to that template).

2. The ability to start downstream pipelines so that when one pipeline has finished successfully (or failed depending on the downstream requirement), one or more downstream pipelines can be triggered to start - this is not available in Jenkins, but is with GoCD. I did accomplish this with BitBucket Pipelines using the API but it was not idea in the fact that I had to keep a separate script with a list of downstream pipelines to notify which would have been a management headache. It would be better if a downstream pipeline could register a webhook with an upstream pipeline for notifications of a successful, failed or either status.

3. Parallel steps so that i can run several steps at the same time - although i see this is available in your Alpha programme.

GoCD also runs everything directly so environment variables are only passed in if you start the command ' bash -c "echo ${env-var}" ' which causes a nightmare for something simple like `docker login` and then in the next command `docker push`.  Your choice to run in Docker containers solves this and which I love.  GitLab do the same thing as you

I like BitBucket PIpelines, but it has a few more features needed before I can convince my company to move over to it, not-least you have to improve the reliability of your infrastructure with 3 outages in the past 3 months!

[Jun Yang]

Any update about this requests? Thanks. 

[salway]

I haven’t checked. Moved to GoCD