First came agile development, and now it’s all about Git. You’ve heard that it’s great for decentralized teams, prevents merge hell, and is awesome for collaboration. But how do you get started?
Well, Atlassian Git Essentials is for you! Last Thursday, we hosted a live webinar to show you how Git Essentials helps you get Git right. Our very own Amber Buchan, Dev Tools extraordinaire, demoed exactly how JIRA, JIRA Agile, Stash, and Bamboo have come together for your Git needs.
We covered the following:
- Going from issue to code to deployment with Git Essentials
- Git workflow best practices available out of the box
- End-to-end development traceability
- Enterprise readiness
Watch the recording and share it
We know some of you couldn’t make it, so here’s the recording for you and your team to watch. See why Atlassian is your one-stop shop for Git.
Questions from the webinar
There were a ton of great questions from the webinar, spanning from product usage to Git topics. We wanted to share some with you:
Q: Is Git Essentials available to OnDemand users?
A: Yes, Git Essentials is available for Download and OnDemand. JIRA and Bamboo OnDemand along with Bitbucket will give you similar functionalities to those demoed in the video. For more info, check out the Git Essentials site.
Q: If I have JIRA, JIRA Agile, Stash, and Bamboo, what version of the products do I need? Can I configure them to do what the Git Essentials package does?
A: You will need JIRA 6.2+, Stash 2.10+ and Bamboo 5.4+ in order to see these features. You can find the instructions on how to configure your products on the streamlining your development with JIRA page. If you have JIRA OnDemand with Bitbucket and/or Bamboo OnDemand, learn more about streamlining your development with JIRA OnDemand.
Q: How does Crucible work with Git Essentials? Can I still use Crucible code reviews?
A: JIRA integrates with FishEye and Crucible to keep you updated on codes changes and reviews in JIRA’s development panel. You can index your Stash repositories in FishEye for in-depth searching and keep Crucible-style code reviews. But it’s recommended to review code in a Crucible review or a Stash pull request, not both. Learn more about tracking code changes with this blog post.
Q: How does Git Essentials help with versioning of products and builds?
A: Git Essentials has capabilities to help with versioning: JIRA is great for managing and organizing release version (details found here). In addition, Stash provides a clean way to structure your release branches with its branch model and prefixes. With this topology, Stash is able to automatically merge your bug-fixes through your affected versions up to your branch mainline.
Q: Git Essentials’ issue-per-branch workflow sounds great, but what if I use submodules, and each submodule has a repository itself?
A: Atlassian Git Essentials comes with some Git workflow best practices ready to go, but you can always customize it to your team’s workflow. In the case of submodules, you can still use feature branches. You’ll just need to create branches with the appropriate issue key in each of the referenced repositories. JIRA supports mapping of multiple branches in multiple repositories to a single issue.