reusable ‘blocks’ of CI/CD workflows

Question

Hello everyone, I hope you are well!

The dynamic pipeline documentation has some examples of things that can be done, including: Creating standardized and reusable ‘blocks’ of CI/CD workflows that can be defined & shared by platform engineering teams, and then consumed by multiple engineering teams within an organization

That's exactly my situation :D . I'm part of the platform team, and we would like to create these ci/cd workflow blocks and share them with the organization.

For example: Java application, I need workflow the following steps:

- Build & Test

- SonarQube Test

- SAST Tool Test

- Docker Build & Push

- Deploy to K8S

Would each step be a forge app? How do I reference forge apps in the bitbucket-pipelines.yml file? Can you help with what the strategy would be like to create these reusable blocks?

https://support.atlassian.com/bitbucket-cloud/docs/dynamic-pipelines/

Reading the documentation I understood that the repository can only be linked to a "dynamic pipeline provider". How can I share steps with just one provider/forge app?

Gui Eloi · Answer

I know the question was asked a long time ago, but updating the answer in the hope of new people looking for an actual easy solution to this problem can benefit from it.

Bitbucket now allows you to split your pipeline in multiple files:

https://www.atlassian.com/blog/bitbucket/split-your-pipelines-workflows-across-multiple-files

Meaning that sharing a definition within the same codebase has gotten much easier, I know your use case was around sharing across multiple projects, in that case, Dynamic Pipelines and Shared Configuration are still the way to go, but for same codebase modularisation this is a much easier strategy.

Aron Gombas _Midori_ · Answer

If so, @Theodora Boudale posted the best link to follow for a working example: https://bitbucket.org/atlassian/forge-bitbucket-dynamic-pipelines-reference-apps/src/main/

Good luck with your project!

Theodora Boudale · Answer

Hi Wesley and welcome to the community!

I recommend posting your questions in this group, as it is specifically for Forge with Bitbucket Cloud:

* https://community.atlassian.com/t5/Forge-for-Bitbucket-Cloud/gh-p/bitbucket-cloud-forge

As far as I'm aware, forge apps are not referenced in the bitbucket-pipelines.yml. After you deploy and install a Forge app, you can enable the dynamic pipeline in either your workspace (Workspace settings -> Pipelines -> Dynamic pipelines) or in a repository (Repository settings -> Pipelines -> Dynamic pipelines).

We have this repository of sample Dynamic Pipelines apps for Bitbucket Cloud:

* https://bitbucket.org/atlassian/forge-bitbucket-dynamic-pipelines-reference-apps/src/main/

I haven't been involved with dynamic pipelines so I can't answer all your questions, I suggest posting in the community group I shared.

You may also want to consider the Shared Pipelines Configuration feature:

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

This allows you to use pipelines defined in one repo in the bitbucket-pipelines.yml of a different repo in the same Bitbucket workspace.

Kind regards,
Theodora