Embed Size (px)
Citation preview
Tim Pettersen • Developer Provocateur • Atlassian • @kannonboy
Tim Pettersen • Developer Provocateur • Atlassian • @kannonboy
git log
git log
Branching Per Issue
Issues Code
Issues Code
JIRA-456
JIRA-123JIRA-123
JIRA-456
Branch per issue
feature/JIRA-30
stable master branch
isolated feature work
master
Visualize your development
IN PROGRESS
Status People Code
Issue
good old days
Visualize your development
Issue
Sprint Branch Pull Request
Build
2015 style
Visualize your development
Typos happne!
Is the branch green?
Branch name pre-populated
No mroe typos.
No more typos.Less broken build angst.
Automatic Issue
Transitions
Sprint 1.0-milestone_1
work left
time left
Sprint 1.0-release_candidate_3
Sprint 1.0-release_candidate_6
Sprint 1.0-release_candidate_25
An engineer’s day.
An engineer’s day.
write some code update issue
fix some tests
create a PRupdate issue
do some rework
merge the PRresolve issue
important stuff “busy”
work
couple of
weeks
Sprint 1.0-release_candidate_6
Automatic Issue Transitions
master
IN REVIEW DONEIN PROGRESSOPEN
feature/JIRA-30
master
IN REVIEW DONEIN PROGRESSOPEN
Branch created!
Automatic Issue Transitions
feature/JIRA-30
master
IN REVIEW DONEIN PROGRESSOPEN
Pull Request Created!
Automatic Issue Transitions
feature/JIRA-30
master
IN REVIEW DONEIN PROGRESSOPEN
Pull Request Merged!
Automatic Issue Transitions
Sprint 1.0-milestone_25
work left
time left
The really
cool stuff
• View issues in Stash and code in JIRA
• Branches, pull requests, builds and deployments in JIRA too
Let’s recap.
• Create branches from JIRA• Automatically transition issues based on actions in Stash
Let’s recap.
Branch per issue
feature/JIRA-30
stable master branch
isolated feature work
master
Releasing is hard !
!
!
DONE
+ = !
DONE
+ = !
+ = !!
Less defects shipped.
Less release stress.
This is live in JIRA Cloud.
Available in JIRA 6.4+
Development bliss.
Tim Pettersen • Developer Provocateur • Atlassian • @kannonboy
Thank you!
