BitBucket is Atlassian’s offering that encapsulates Git.  They have an entire suite of products that enable end-to-end collaboration.

It has a lot of the same features as GitHUb:
———————————————–
– It is built on top of Git.
– It is used for source code mgmt.
– It has pull requests to facilitate code reviews.
– It has branching and merging.
– It has forking.
– It has webhooks.

But it also has other features as well:
—————————————
– It is directly integrated with Atlassian’s other tools (Jira (task tracking), Confluence (Collaboration), Crowd (LDAP)).
– It provides a tighter structure to its repositories.
– It provides tighter security through it’s integration with Crowd.
– It facilitates collaboration through its integration with Jira and Confluence.
– It provides end-to-end tracking when a branch is created from a Jira ticket.

Pros:
—–
– It can be hosted in Atlassian’s cloud environment or it can be on-prem at your company.
– It has a high availability Data Center version.
– It has unlimited repositories for free for up to 5 users.
– Is is supposed to have better searching but we have found it lacking in regards to wildcard searches.
– You can import your code from more SCM systems than GitHub.
– Powerful Jira integration can update Jira ticket status on BitBucket commit.
– Offers in-line comments directly in the code review window.
– Integrates directly with Trello.
– Integrates with Slack.
– Better pricing (GitHub private repos can be pricey).
– Powerful ACL thanks to integration with Crowd (think LDAP server with groups).

Cons:
—–
– Smaller community
– Fewer plugins
– Wildcard searches

My Take:
————
Using the Atlassian suite enables you to have end-to-end tracking of source code changes that starts with the entry of the requirement into a Jira ticket.

Next episode:  CI/CD Basics