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.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

How can I ensure that a change that spans multiple repositories is deployed synchronously?

Edited

I have many repos which have changes that will require other services/API endpoints to be in place to work fully at the system level (microservices architecture). How, in Jira, can I ensure that I don't end up deploying a half fixed system. Realistically, I want something like a deploy-on-epic completion interaction with the CI where only when a particular epic is complete can all changes contributing to that epic be deployed to live.

Anyone have any ideas/solutions etc? Of course, there is a chance that there is a fundamentally simpler solution to this and I may have already got stuff wrong.

 

Thanks

0 comments

Comment

Log in or Sign up to comment