1 / 57

Stash - We Code Together

Coding is simple and great if it's just you working on the code. It is getting much more complex when a whole team or even several teams are working on the code base. You want to be sure, that everybody knows about code changes, the quality is the same all over the code base and a merge shouldn't stop the whole team from working. Atlassian's tools can help you out. <br><br>This presentation shows how you can use Stash and Bamboo to happily code together in a team. You don't have to worry about broken builds on your master branch or that your graduate accidentally merges his changes that get automatic deployed. Everybody understands each part of the code base and the code got reviewed before it hits your master branch.

svenpet
Download Presentation

Stash - We Code Together

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. We C de T gether

  2. Sven Peters Happy Ambassador @svenpet http://svenpet.com

  3. Life as a Hacker is great !

  4. Simple Workflow! writing code committing code

  5. Simple dependencies! stops just you ... so what? writing breaking code fixing code code code

  6. Code Quality like code

  7. Lonesome Cowboy

  8. The trouble starts with the team

  9. Life as a Team Coder

  10. Multiple changes! writing merging code changing code code code

  11. Rely on each other! stops the team writing breaking code fixing code code fast code

  12. Code Quality! writing reviewing code code Opinion Opinion Opinion

  13. It's not your code It's your team's code

  14. get help C D E T GETHER

  15. C T GETHER D E Bringing code together Sharing code with others Protecting your code

  16. C T GETHER D E Bringing code together

  17. Branching is cool!

  18. MERGE HELL

  19. everybody stops to work until merge is done Merge Fear Disease afraid that the build will fail waiting until the code is done done

  20. A branch for every task

  21. Branches have short lives ~ 2 days

  22. DVCS rocks Git Mercurial

  23. find out! Will the build fail if I would merge now? ... and stop the rest of the team!

  24. find out!

  25. plan branches

  26. virtual commit

  27. Bamboo

  28. C T GETHER D E Sharing code with others

  29. Do you have such a team member? I've written that code. It's faster when I just fix it. I can't tell you how this works. It's too complicated. This is a very sensitive area... You can easily break things

  30. Do you have such a team member? I want to protect my job!

  31. Do you have such a team member? him! Fire

  32. feel better Learn Discuss your code changes Better quality

  33. use Pul Requests Discuss your code changes before they get merged!

  34. use Pul Requests create what do you think?

  35. use Pul Requests invite what do you think?

  36. use Pul Requests discuss & approve what do you think?

  37. use Pul Requests merge what do you think?

  38. use Pul Requests involve I know @Ben has already written an algorithm for that

  39. Dem Time

  40. Share and Collaborate on Code is great !

  41. Share and Collaborate on Code should be easy and fast

  42. Simple Workflow Merge Pull Request Branch

  43. Simple Workflow No Roles Merge Pull Request Branch

  44. C T GETHER D E Protecting your code

  45. Simple Workflow No Roles Merge Pull Request Branch

  46. Simple Workflow No Roles Merge Pull Request Branch

  47. Simple Workflow Some Roles Merge Pull Request Branch

  48. Do you want your graduates merge into the automatic deploy branch?

  49. BranchPermissions

More Related