Shared Pipeline Configuration Model
Asked by brian:

Shared pipeline configs are great, but I'm finding it difficult to understand what capabilities there are for overriding components of a shared pipeline. For example:

\* Can I add more steps?  
\* Can I modify existing shared steps?  
\* Can I define steps that can be referred to without being part of the original shared pipeline?

I haven't been able to find documentation on how the pipeline is merged, and what the "effective" configuration might look like in different scenarios.

Best case scenario, I'd also love to be able to share scripts as part of the shared pipeline repo. I know I could manually clone them in a given step, but that adds a lot of time to the execution. Perhaps smaller scripts can be added to definitions in the shared pipeline file?  

I'd love to hear what other people are doing with shared pipelines to handle exceptions and edge cases in individual repos.


Answers:
author: Caterina Curti
body: Hi [@brian](/t5/user/viewprofilepage/user-id/5408718) ,

I have an update for you and everybody on this.  

We recently introduced [Dynamic Pipelines](https://bitbucket.org/blog/introducing-dynamic-pipelines-a-new-standard-in-ci-cd-flexibility) and all the use cases you mention are doable.

I just published [this article](https://community.atlassian.com/t5/Forge-for-Bitbucket-Cloud/Share-a-step-across-pipelines-Dynamic-Pipelines/ba-p/2712403) explaining how to add a step and all other options can also be implemented by adapting the JavaScript logic.

Hope you'll find this useful,  
Caterina  

comments: author: Aurimas N_
body: Honestly dynamic pipelines are great, but it feels like they are mentioned everywhere people have questions or feature requests, feels a bit like the general functionality and feature set of base pipelines is not priority, but instead "do it yourself with dynamic pipelines" is offered as a solution to many shortcomings of bitbucket pipelines.


author: Theodora Boudale
body: Hi Brian and welcome to the community!

This feature was recently introduced and it is not possible at the moment to customize elements of the imported pipeline, add more steps, or export specific steps.

We have a feature request for the ability to share individual steps and combine an imported pipeline with additional steps:

* <https://jira.atlassian.com/browse/BCLOUD-22855>

You can add your vote to that feature request (by selecting the **Vote for this issue** link) as the number of votes helps the product managers better understand the demand for features. You are more than welcome to leave any feedback, and you can also add yourself as a watcher (by selecting the **Start watching this issue** link) if you'd like to get notified via email of updates.

Implementation of features is done as per our policy [here](https://confluence.atlassian.com/support/implementation-of-new-features-policy-201294576.html) and any updates will be posted in the feature request.

You can also check the documentation on shared pipelines configuration, it includes some FAQs:

* <https://support.atlassian.com/bitbucket-cloud/docs/share-pipelines-configurations/>

Please feel free to let me know if you have any questions.

Kind regards,  
Theodora


Tags: bitbucket-cloud

bitbucket-pipelines

cloud