By Marcus Bertrand, Support Engineer on August 30, 2013
We’ve got two announcements today about services we will be shutting down in the coming weeks. Their use has waned, and it’s time to put them out to pasture.
The Bitbucket Google Group
A few years ago we started this forum to allow our users to interact with each other and the Bitbucket developers. Since that time, much has changed and we’ve added many more avenues for getting help with Bitbucket as well as Atlassian’s other products. To that end, on 1, October 2013 we will permanently set this forum to read-only mode. In its place, we encourage you to use Atlassian Answers for the same questions you’ve always had. Answers has a few advantages over the forums, such as:
- You aren’t talking to an empty room – Of all the questions posted on Answers, over 80 percent receive at least one answer, with almost half that answered within an hour!
- Karma! – Points are awarded to our more active users. This establishes credibility in the community.
- Atlassian swag – As you climb the Karma levels, you get free Atlassian swag like t-shirts, backpacks and jackets.
- Built-in community – Since you’ll be posting in an Atlassian-wide forum, you can get help with topics like deployments, tagging, and other best practices by tapping the knowledge of the greater Atlassian community.
- It’s FREE! – No explanation needed.
To sign up, simply visit https://answers.atlassian.com, click login, then sign up under the login boxes. Once your email is confirmed, you’ll have full access to Answers, not to mention all the Atlassian services linked with Atlassian ID, including: support.atlassian.com (for ALL support, including Bitbucket), jira.atlassian.com for bug reports for Atlassian’s other products, confluence.atlassian.com for leaving comments on our documentation, and more in the future.
Subversion to Mercurial bridge
For some time now, the Subversion to Mercurial bridge we offered hasn’t worked in numerous situations and cases. So, we’ll be shutting it down officially on 1, October 2013. This should only affect a very small group of users in the community, but it is important that they know this is coming.
By Charles on August 27, 2013
We’re planning scheduled maintenance Friday, August 30, 2013 at 03:00:00 UTC lasting no more than one hour. During this maintenance window we will restart our master PostgreSQL database to apply a setting change and upgrade our RabbitMQ server.
Thanks for your patience as we work to improve Bitbucket’s reliability.
By Justen Stepka, Product Manager on August 21, 2013
The Bitbucket team is in the midst of building out some larger features, and recently took an opportunity to conduct another Innovation Week to ship a bunch of new features!
What’s Innovation Week?
Every few iterations we set aside an iteration for developers to work on whatever they desire — feature enhancements, new features, bug fixes, internal dev-speed, performance improvements, whatever they are interested in. Developers can fly solo or form groups to tackle larger projects. The end goal is to have a shippable feature or improvement by the end of the week. Here’s what our engineers shipped this time around:
When we revamped user profiles a few months ago we exposed team member information that wasn’t previously available, and people noticed. This project circles back around and gives users the ability to make their profile pages private.
Improved SSH and deploy key security
SSH and deploy keys are are now immutable. To bolster security even further, Bitbucket will also send notifications when a new SSH key is added to an account.
A few Innovation Weeks ago we added in-page notifications of pull request comments and updates, which gets quite a bit of use within the Bitbucket team. This time around, we built on that work by slicking up the UI and loading new comments in ajaxily to avoid full page pops, speeding the interaction up tremendously for those teams using pull requests.
Pull request POST hook
Now users can set up a POST hook to any pull request action (comment, update, approve, etc). This feature builds on the infrastructure improvements we made during the notifications refactor.
Improved hooks admin interface
Previously called “Services”, we’ve renamed this feature “Hooks” based on user feedback. We’ve also rolled out a new interface that provides a scannable list of integrated services, and hides the complexity until you actually need it.
We had a lot of fun with this Innovation Week, and hope you find some of these features and improvements useful. Does this kind of thing sound fun to you? We’re always looking for great engineers. Check out Atlassian’s career page to learn more.
By Jesper Noehr on August 15, 2013
When it comes to your account on Bitbucket, security and privacy is paramount — which is why we’ve added a full audit log for any changes made to personal and teams accounts.
Changes made by yourself, or third party applications configured via OAuth will be recorded in the audit log. Some of the events you’ll see when reviewing your accounts are:
- Basic account information (name, location, website) updates
- Changes to email addresses
- Links with third party accounts (Google, Twitter, Facebook)
- Addition of OAuth services integrations
- Groups & general access list changes
- Creation and deletion of repositories
In addition, we also record the IP address associated with the change so you’ll know exactly where the change has come from.
Keep track of your team
The audit log also works for team accounts: If you manage repositories under a team account like we do, you can now see who changed the team name, who created a group, or who deleted a repository.
By Justen Stepka, Product Manager on August 14, 2013
Some issues draw more attention than others on the Bitbucket issue tracker, and a lot of that attention manifests itself as simple “+1″ comments — the quickest, easiest way for people to voice their agreement with a problem or idea. Unfortunately these comments tend to clutter the issue, and spam people with useless notifications.
During our last ShipIt hackathon, one of our developers decided to do something about this and added voting capability to issues in Bitbucket! We know this is going to improve our interaction with our users, and we’re pretty sure anyone with a public Bitbucket issue tracker will feel the same way.
When using the issue list view you’ll see the total votes for a particular issue, and have the option to sort by votes. As a bonus, we did a migration of any “+1″ issue comments over to votes to help get things started. Happy voting!
By Justen Stepka, Product Manager on July 16, 2013
After over 700 requests to replace Gravatar from Bitbucket users like you, we’re excited to announce a new avatar picker in Bitbucket. Now you can upload and crop images to personalize your user profile and free private repositories.
Upload any JPG, GIF, or PNG via drag-and-drop or the file browser, then easily resize until your image is just right. Bitbucket will give you a large-scale preview of how your avatar will be displayed throughout Bitbucket on commits, pull requests, and activity streams.
Of course if you’re already using Gravatar with a validated Bitbucket email address, you can count on backwards compatibility (in other words, your existing profile picture is safe).
By Justen Stepka, Product Manager on July 7, 2013
Many of you enjoyed playing the game Bit’s Quest during our data center migration and have asked us if the game would be made available after the migration. Good news, we’ve made the game available at bitsquest.bitbucket.org.
What’s Bit’s Quest?
By Justen Stepka, Product Manager on July 2, 2013
In a few days we’ll flip a switch and migrate Bitbucket to a new hosting provider. During this migration Bitbucket will be unavailable up to six hours starting Sunday, July 07, 2013 at 19:00:00 UTC.
UPDATE: the migration is now complete — thanks for your patience everyone!
Over the last several months we’ve put together a detailed plan that limits downtime to no more than six hours. Why so long? Bitbucket has maintained a synchronization of our filesystems and databases between the two data centers for several weeks. When we bring down Bitbucket at the current data center, it will take a few hours to finalize the replication between the two data centers before we can bring up the new location.
Once the synchronization is complete, we will bring the new location up and perform a series of integrity and performance tests to assure the new hardware is ready to go before making it publicly available.
Why we’re moving
Bitbucket has seen amazing growth since introducing free unlimited Git repositories for individuals and small teams. With over a million users now utilizing Bitbucket to build better software, moving our data center allows us to:
- link Bitbucket servers to the fastest internet connections possible
- co-locate with our Atlassian OnDemand platform for customers looking to integrate with JIRA
- co-locate with a direct link to Amazon Web Services
- scale Bitbucket’s infrastructure to 10s of millions of users
How this affects you
With the move to a new data center comes the addition of IP addresses.
Incoming IP addresses will be:
Outgoing IP addresses will be:
When pushing and pulling over SSH you’ll see a warning similar to this:
Warning: the RSA host key for ‘bitbucket.org’ differs from the key for the IP address ’22.214.171.124′
The warning message will also tell you which lines in your ~/.ssh/known_hosts need to change. Open that file in your favorite editor, make the necessary changes, then retry your push or pull.
During the migration, we’ll post updates on Twitter and our status site providing the current status so you can follow our progress.
Thanks for your patience as we work to increase Bitbucket’s performance and reliability. Please contact us at email@example.com if you have any questions about or during the migration.
By Justen Stepka, Product Manager on July 1, 2013
Atlassian has released a new version of the DVCS Connector that connects Bitbucket and GitHub to JIRA. This update addresses a variety of configuration and performance bugs for our OnDemand an On-Premises customers:
- Commit messages are no longer dual processed by smart commits when using forks.
- Configuration screens use the Atlassian Design Guidelines (ADG).
- OAuth authorizations can be re-confirmed if removed from Bitbucket or GitHub.
- OAuth key and secrets can be updated for existing configurations.
- Permission checks have been improved when adding repositories without proper access.
Get the DVCS Connector
If you haven’t already, make sure to install the JIRA DVCS Connector in order to:
- Track commits, monitor source code edits, and drill through to source files straight from JIRA.
- Push commits to JIRA simply by referencing issue keys in commit messages.
- Map unlimited public and private Bitbucket and GitHub repositories to JIRA projects.
- View Bitbucket and GitHub activity in the JIRA Activity stream.
By Justen Stepka, Product Manager on June 26, 2013
It’s a big day for SourceTree for Windows: We’re releasing version 1.0 into the wild today. Every developer knows that hitting 1.0 is a formative moment for every product, and we think we’ve got a cracking release for you to check out. The full release notes have the complete story but here are the highlights:
The big headline feature in this release is support for Mercurial, finally bringing the Windows version into line with the Mac. Thanks to everyone who has been asking for this for their patience – to make up for it you get early access to a few Mercurial enhancements which are pending the next version on Mac, such as optimized, full-log previews of incoming / outgoing changes. Enjoy!
Push and pull counters
You can now see how many changes you have to push or pull on the toolbar and on your bookmarks. Never forget to push again!
Automatic remote fetching
SourceTree can now periodically fetch new commits from your default remotes in the background so you’re always up to date with what’s going on.
Stage and unstage shortcut buttons
By popular request we added some extra buttons to make staging and unstaging at a file level faster in Git.
… and lots more!
We really hope you enjoy this milestone release of SourceTree for Windows. Let us know what you think!
Note: If you’re still on 0.9.2.3, please see our previous blog post for how to update.