Starting February 18, 2014, Bitbucket will remove the ability for individuals to log into a team account with a username and password. We are taking this action so that we can bring you Atlassian ID later this year. Atlassian ID is single sign-on across all our OnDemand services such as Bitbucket, JIRA, HipChat and Confluence, one of the most popular feature requests on Bitbucket!

What does this mean to you

• If you access your team while logged in as your personal account, you don’t have to do anything.
• If you login to your team with a username and password, you will need to appoint or create an administrator for your team. We’ve added a warning banner to your account which will walk you through this process. You will also receive an email with instructions on what to do next.

Other housekeeping

As part of this change, any team that has no groups or individual members has been converted to an individual account. This is a very small subset of users who will notice absolutely no change in their daily work.

Help I’ve lost my way

Bitbucket’s support team is here to help you troubleshoot any problems or questions you may have with this migration. Simply file a support ticket and you’ll be good to go.

On Saturday, at approximately 8:30PM GMT, Bitbucket will perform non-disruptive network maintenance.

We will be performing physical cabling work in our patch racks in preparation of expanding our network capacity.  We don’t anticipate that this will have any affect on site performance or availability. If you have any con

To celebrate the new year (admittedly a little belatedly), how about a new major version of SourceTree for Windows? We have a doozy for you to start off 2014.

git-svn support

You can now use SourceTree for Windows to interoperate with your old Subversion projects via git-svn. This works by letting you work with a Git repository locally, but you can interact with a remote SVN repository via clone, push, and pull, thereby combining the benefits of a fast and flexible local DVCS, while still collaborating effectively with your projects that are still running legacy repositories.

Command line interface

You can now call SourceTree.exe from wherever you installed it on the command line, and by default it will open up the nearest containing repository for your current directory. You can also specify a different path, and ask SourceTree to immediately navigate to certain views or run certain commands, like so:

SourceTree [-f path] [ <command> [<command_params>] ]

clone <url>

status

log

search [<pattern>]

filelog <file>

commit

Translations

Thanks to your response to our call for translators, SourceTree for Windows 1.4 now comes in six languages: English, Japanese, Chinese, French, German, and Russian. The latter three are not 100 percent complete yet, but the major elements are translated; If you’d like to help fill in the remaining blanks, please join in the translation effort!

Patch file support

You can now create and apply patches within SourceTree – You can work effectively with patches comprised of uncommitted working state, and with patches containing one or more complete commits. SourceTree gathers all the options for generating a patch into an easy interface, and does the work of recognizing the relative paths and strip options when you’re applying a patch so you don’t have to work it out manually.

You can find the patch features on the Actions menu, labelled Create Patch and Apply Patch.

Archive support

Would you like to export a full copy of your source without all the Git/Mercurial history and metadata, either at the current state or at some other point in history? Archive is the feature you need for that, available either on the main menu (Repository > Archive), or on the context menu against a commit in the log (right-click a commit and pick Archive).

Analytics

We want to make SourceTree an even better product for you, and to do this we’d love your help in finding out how you use our product. In the latest version you’ll get a popup asking if it’s OK to gather some data about how you use the product. We want to emphasize that no personal data is taken whatsoever.

Miscellaneous

We also added a bunch of other smaller things, such as:

• An optional spell checker in the commit dialog
• The ability to bookmark open repositories which you opened with File > Open or via the command line
• Configurable conversion of tabs to spaces in the diff view
• Improved multi-monitor support
• and more…

We hope you like the new version of SourceTree for Windows!

We’re planning scheduled maintenance Saturday, February 8, 2014 at 18:00:00 UTC lasting no more than two hours. During this maintenance window we will restart our master PostgreSQL database and Redis data structure server to apply system updates.

Thank you for your patience as we work to improve Bitbucket’s reliability.

A picture is worth a thousand words, and this is one cliché that the Bitbucket team takes to heart. Every day, we use images to help make things clearer a screen shot of a feature gets added to your code review so reviewers know what to expect, or an illustration of steps involved to reproduce a bug when creating a JIRA issue. Images can liven up the documentation on a wiki, or just help make a point.

Our guess is, your team does this too. So we’re happy to announce that today, we’re making it really easy to do all these fun and useful things by uploading your images right to Bitbucket.

Say it with .JPEGs (or .PNGs, or .GIFs)

You can upload images anywhere you see the markup toolbar – just click the image button to get started. Select an image from the file chooser or drag one to the dialog, or you can drag an image right into the comment box! We’ll upload your image and insert the link into your markup, ready to be seen.

Image privacy

Uploaded images use the same security settings as the repository they are added to. If your repository is private, only people with access can see the images you upload there.

We’ll be performing network maintenance on Sunday, February 23, 2014 at 04:00:00 UTC to expand our network capacity. There may be brief interruptions in connectivity during this maintenance window

With Bitbucket you can edit any file, anywhere, all you need is your browser. But we’ve been missing one thing: the ability to add new files from the web using the online editor. So we fixed it.

Starting today, you can now add new files directly to repository from the source browser; no command line, no cloning, no local editor.

After clicking New file, Bitbucket’s online editor will ask you the name of the new file you’d like to create. Syntax highlighting and diff view are all an integrated part of the code editing experience.

Once you’re happy with your edits, commit directly to the branch you’re editing on, or create a pull request and select your reviewers. If you don’t have write access, Bitbucket will automatically create a fork for you and commit your changes before submitting a pull request.

In addition to being able to add new files online, we added the ability to rename or delete unwanted files. To rename or delete a file, use the source browser and click on the Edit menu options.

Get started now

Join the growing number of teams that host their code on Bitbucket and stay better connected with unlimited private repositories free for 5 users.

In October we introduced our feature branching workflow – a simple and fool-proof way to get started with Git branching for those using Bitbucket with JIRA, SourceTree and Bamboo.

Today, we are excited to bring you our latest integration feature; the development panel in JIRA. Keep team leads, project managers and product owners informed about development progress taking place in Bitbucket with this new JIRA integration.

All the right info in the right place

You’ve just been asked the ever pressing question, “What’s the status of this issue? Is the code review complete? Are we ready to ship?” From each JIRA issue, you can see branches, commits, status of pull requests, builds, and deployments all at a glance.

No longer will you be clicking through tabs and scrolling for updates, nor will you have to dig through your repos and reviews. Within seconds of opening a JIRA issue you can check out the progress of any JIRA issue and where it is in development. All the most relevant development information is surfaced from within JIRA.

Details you need; traceability you want

The development panel is perfect when you are looking for a quick update, however sometimes you need even more specific details. Deep diving into any of the items shown in the new development panel is as simple as clicking on the link to learn more.

You can even move seamlessly between JIRA, Bitbucket and Bamboo with bi-directional links between your issues, source and builds.

More best practices for your team

Everywhere teams are making the switch from Subversion to Git. If you’re new to Git and want to learn more, check out Atlassian’s Git Essentials, our solution to implementing best practices with Git for your development team.

Git the integration

The new development panel for JIRA is available today for Atlassian OnDemand customers. For JIRA download users, you can freely get the JIRA DVCS Connector via the Atlassian Marketplace.

Come join us at Atlassian and work on SourceTree, our free Git & Mercurial client for Windows and Mac! We’re looking for a development team lead to help change the way people develop software and spread the adoption of Git and Mercurial. You will be working in a fast paced environment where every line of code you write will be appreciated by a developer community of millions.

You will be responsible for leading a small team of passionate developers who are tasked with designing and implementing the best Git and Mercurial client on the planet. In this role you will spend 70% of your time working on improving the product and 30% of the time leading your team. If you have previous team leading experience, great –  if not, this is a great opportunity to give it a go.

What you will do:

• Lead a small and agile development team in building the best Git & Mercurial client
• Dive into the Objective-C and C# codebase to cut some kick-ass features
• Work with Product Management in building the roadmap that ensures SourceTree is loved by its users
• Grow a motivated team that continuously looks to improve and challenge themselves
• Collaborate and coordinate with other product and cross functional teams
• Foster the Atlassian culture and ethic of the team

Key skills:

• Deep understanding and passion for Git and Mercurial
• Experience following current project management practices (Agile, Scrum, Kanban, Lean etc.)
• Extended knowledge of Objective-C or C#
• Knowledge of Cocoa or WPF
• Experience in working with distributed teams would be a plus

This is what we look for in every Atlassian:

• Get It Done (Initiative)
• Think Like An Engineer (Analytical)
• Be David, Not Goliath (Innovative)
• There is No I in Culture (Teamwork)
• You Are Our Ambassador (Communications)
• Legendary Service (Customer Service)

On March 7th at 22:00 UTC, we’ll be updating our SSL certificates to replace ones that will be expiring soon. It’s likely that you won’t notice any changes and won’t need to take any action. However, if you’re using Mercurial over HTTPS, you may see this error message:

abort: certificate for bitbucket.org has unexpected fingerprint
67:b3:bf:9f:c5:38:0e:4c:dd:4e:8a:da:3d:11:1b:c2:a5:d1:6c:6b
(check hostfingerprint configuration)

If you see this error, you’ll need to update the host fingerprint for bitbucket.org in your ~/.hgrc or Mercurial.ini configuration file:

[hostfingerprints]
bitbucket.org = 67:b3:bf:9f:c5:38:0e:4c:dd:4e:8a:da:3d:11:1b:c2:a5:d1:6c:6b

Thanks, and happy forking!

We will be performing a 30 minute maintenance window on Saturday, March 22, 2014 at 20:00:00 UTC. We will  be applying new configuration settings to our database.

With SourceTree 1.4.0 for Windows released just a few weeks ago, we’re excited to announce that 1.5.0 is ready to go. We’ve been steadily playing catchup with the Mac version and we’re happy to ship some highly requested features.

Interactive rebase

The interactive rebase feature is now available on SourceTree for Windows. Need to mess with your local commits before you go and push them? Go ahead! To use this feature you can either click the Repository menu and hit Interactive rebase to rebase from your last upstream commit, or right-click on a commit in the log and go to Rebase children of <sha> interactively.

Subtree

A more flexible option to Git’s submodules, subtree allows you to carry out a whole host of tasks when including other repositories into your own repository. You can pull down changes, or even commit and push changes to an unrelated repository. Like submodules, you can add a subtree either from the sidebar or from the Repository menu.

Tab reordering

Keeping your tabs organized is an absolute must when dealing with a lot of repositories. To help with that you can now reorder your tabs; Just drag and drop them to wherever you want.

Get SourceTree for Windows or Mac

Grab the latest version from sourcetreeapp.com!

On April 9th at 01:30 UTC, we’ll be updating our SSL certificates as a response to the Heartbleed bug. This change is the final step in ensuring that our systems are not vulnerable. We apologize for the short notice.

It’s likely that you won’t notice any changes and won’t need to take any action. However, if you’re using Mercurial over HTTPS, you may see this error message:

abort: certificate for bitbucket.org has unexpected fingerprint
45:AD:AE:1A:CF:0E:73:47:06:07:E0:88:F5:CC:10:E5:FA:1C:F7:99
(check hostfingerprint configuration)

If you see this error, you’ll need to update the host fingerprint for bitbucket.org in your ~/.hgrc or Mercurial.ini configuration file:

[hostfingerprints]
bitbucket.org = 45:AD:AE:1A:CF:0E:73:47:06:07:E0:88:F5:CC:10:E5:FA:1C:F7:99

Thanks, and happy forking!

We have now completed all changes necessary to secure Bitbucket from security vulnerabilities related to the Heartbleed bug. Changes made to Bitbucket include;

• Upgrading Bitbucket’s load balancers to use new OpenSSL libraries
• Reissued and updated our SSL certificates
• Resetting long term authentication cookies

As a result of us removing the sessions related to authentication cookies, all users have been forced to re-authenticate when using bitbucket.org from a browser. We are also recommending, but not enforcing, that all users change their passwords.

Starting today your pull requests will always have the most recent and relevant code, and your reviews will be more efficient. With automatic updates, pushing to a branch with an open pull request will automatically include those commits in the open pull request. This way your reviewers will always see the most recent changes to the branch in the pull request.

The most important thing about a pull request is the discussion that it generates: As you get feedback from other developers about changes or improvements that should be made, you’ll be generating new commits which should be part of your review. Now you’ll automatically see those commits in the pull request with no extra steps.

More best practices for your team

Everywhere, teams are making the switch from Subversion to Git. If you’re new to Git and want to learn more, check out Atlassian Git Essentials, our solution to implementing best practices with Git for your development team.

Starting today, we will be migrating all repositories to a new storage system which will allow us to improve the service and reliability of Bitbucket.

Over the next weeks, you can expect the following:

• Repositories will be migrated to our new storage system on a rolling basis and not all at once.
• During each repository’s migration, it will be placed in read-only to ensure data integrity and reduce risk during the migration.
• Once your repository is on the new hardware, and we’ve verified consistency, it will automatically return to its original read/write state.
• On average, each repository should take less than 10 minutes to migrate, but repositories with frequent updates may take longer (up to 30 min in rare cases).

Due to the nature of the migration, we are unable to provide specific timelines for when individual repos will be affected. However, we expect no more than a 10 minute disruption when your repository will be placed in read-only mode.

Thank you all for your patience and support! We are working hard to constantly build a better Bitbucket.

If you have any other questions or concerns, please come to support@bitbucket.org.

The more code you can see on your screen, the easier it is to work with it. That’s why we broke away from our traditional fixed-width pages, and redesigned every page on Bitbucket to expand to the full width of your screen, as wide as your browser will allow.

See more of your code

When you’re in the zone, having to scroll horizontally to see all your work can really break your focus. Bitbucket’s new expansion capability makes it easier to view source, conduct code reviews, or edit files. Other pages, such as the listing of all your open pull requests, are now much easier to read now as well.

Sidebar based navigation

To reduce scrolling even more, we moved the navigation and action links from the top of the page into a collapsible bar on the left side. Using Bitbucket’s keyboard shortcuts, the sidebar can be expanded or collapsed simply by pressing “[“.

Whether expanded or collapsed, the bar is anchored to the side of your repositories, giving you instant access to common actions like creating a pull request – even when you’ve scrolled waist-deep into a diff.

Dead simple READMEs

READMEs are a great way to make your project more attractive, and jumpstart other devs who want to pitch in. So we felt they deserve some special treatment.

If your project doesn’t already have a README, we’ve made it brain-dead simple to get one started. Just use Bitbucket’s online code editing features, and a template that includes suggestions for key repository details such as installation or configuration instructions, contact information, license information, and acknowledgements.

For repositories that already have a README, we’ve added a direct link to our online editor so it’s easy to keep your project details up to date. By default, READMEs will be created in Markdown. But if you’ve got an ASCII or reStructured file, that’ll work fine too.

Dashboard insight

Most of us have an ever-growing set of repos, and finding the one you need to work with can be a pain. The redesigned dashboard now features your repositories front and center, with the most recently active repos at the top. And the same quick search and filters are still there, making it extra easy to find repos you own or watch.

To make accessing the dashboard lightening-fast, we’ve added shortcut links to the global header so you can jump there from any page on Bitbucket. We’ve also moved the activity feed to the right side with a high-level overview of what’s taking place across all the repositories your team is working on. 

Try Git out for free

Join the growing number of teams that host their code on Bitbucket, and stay more connected with unlimited private repositories free for five users. Or if you want to run Git on your own servers, check out Stash, our on-premises source code management for Git – it’s secure, fast, and enterprise grade. 

or

Help spread the message on Twitter

In order to improve and maintain the overall performance for everyone who uses Bitbucket, we are rolling out size limits on newly-created repositories. Starting today, repository size limits will be:

• Soft limit of 1 GB – In-product and email notifications will give you a heads-up that you’re approaching the limit.
• Hard limit of 2 GB – Pushing to the repository will be disabled until you’re back under the limit.

If you already have a repository that is larger than the 2GB limit, your repository has been grandfathered so you won’t have any issues. Should you find your new repository approaching the 1GB soft limit, check out our documentation on how to reduce repository sizes or our blog “How to handle big repositories”.

Of course, Bitbucket still offers unlimited private repositories free for five users!

In the last few days, Bitbucket experienced intermittent database issues which caused the site to become unavailable for several minutes at a time. These outages are far beyond what we consider acceptable as a service provider, and we sincerely apologize for any inconvenience this caused.

We continue to investigate these database issues and our goal is to resolve these issues permanently as soon as possible. As part of our on-going investigation we will be be making Bitbucket unavailable for up to four hours starting Saturday, June 14, 2014 at 10:00:00 Pacific to make database configuration changes and upgrades.

Please subscribe to http://status.bitbucket.org to receive instant updates via email, SMS or RSS as we progress through the downtime. Thank you for your patience as we work to increase Bitbucket’s performance and reliability. Please contact us support@bitbucket.org if you have any questions or concerns.

Recently our teammate and Bitbucket engineer Erik Van Zijst had the opportunity to present at Euro Python 2014 in Berlin. Check out this video of his session on the Inner Guts of Bitbucket and get a detailed overview of our current architecture at all layers from Gunicorn and Django to Celery and HAProxy to NFS.

In addition to the inside scoop into Bitbucket’s inner workings, this video covers some war stories and shows how we too have to learn things the hard way sometimes.