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

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,475
Community Members
 
Community Events
176
Community Groups

build release process in jira-software cloud

Edited

Currently we package a build through our release planning process, and then put it to testing. Due to timeline considerations we get pressed to push the build forward even though all tickets are not fully tested. We are not in production yet so we had a little leniency, and low risk, up until now. We need a way to uncouple the release package if a ticket or tickets don’t pass test, and push the rest of the tickets forward. There were talks of release candidates, putting changes into a master branch and controlling pull requests, and separating resources between development and release, in order to pass audit. Even with a way to pull out tickets that don’t make the test, regression testing on the final package would still need to be considered in the timing, due to the interconnections of code and fixes. I'm looking for a better approach in handling this situation.

 

0 comments

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events