Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Approaches for implementing and managing patterns for Bitbucket Pipeline projects

Hey Everyone. I'm searching for insights from other Bitbucket Pipeline users on how they manage pipelines at scale across all their teams.

As part of our rollout we are thinking of defining a series of templates for our different app types (eg. Angular website, Spring Boot API) and each will have a code repository skeleton and also a pipeline skeleton. Our developer engineering portal can trigger these to be rolled out as needed.

This all seems pretty straightforward. Some of the things that I'm curious about are:

  • How to manage pipeline.yml drift as either teams customize their pipeline or new versions of the pipeline skeleton are released. I could see something like renovatebot for pipelines being useful.
  • How to ensure important steps like change control approvals aren't removed from the pipeline? Maybe a combination of pull request controls and static analysis rules?

Any thoughts appreciated.

1 comment

It looks like part of Atlassian's solution for this is this upcoming feature: 

Looking forward to more details

Like Avi likes this


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events