You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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:
Any thoughts appreciated.