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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I have a client new to the Atlassian family. They jumped into a fairly complex Java Specs to manage a set of several hundred API endpoints. It is working fine, but any changes are being developed and applied directly in the production spec.
Now that they are past the initial setup, they would like to create a good development environment. I would like to know how others are doing it. They use gitflow in app dev.
1. are you using non-master branches of the same repo for development or a whole different repo? How are your prod and non-prod java spec scan repos configured?
2. when testing, do you build your non-production jobs on your production Bamboo box or a separate non-prod box?
3. have you automated any required changes in the non-prod code (like the URL of the bamboo server if you use a different one)?
If you know of a resource in the Atlassian documentation that helps with this, I would appreciate a reference. I have come up empty.