Posts by Tim Pettersen
At Atlassian, one of our design principles is to gracefully reveal depth. As we've iterated on our UX, certain Bitbucket power user features that strayed too far from the happy path have been hidden away behind a dropdown or keyboard shortcut. There they bide their time until an adventurous user stumbles upon it through a capricious key press or mouse click (or someone reads the docs). Here's six of my favourite Bitbucket Cloud features, that you've possibly never heard of:
I'm a huge fan of Node.js and npm, so I've built a little npm for Bitbucket
add-on that adds module metadata, dependency information and download
statistics to the npm modules hosted on Bitbucket. What makes the add-on
special is that it's built in a slightly peculiar way: it's 100%
XHR techniques (CORS,
window.postMessage, and API proxying) to
exhibit some pretty powerful dynamic behaviour.
A quick two months after 2.6, Git 2.7 has been released with a plethora of features, fixes and performance improvements. Here's some of the new stuff we found interesting on the Bitbucket team.
I've written hundreds of Bash scripts over my career, but I still suck at Bash.
I have to look up the syntax for simple logical structures every single time. If
I want to do anything fancy with
sed, I have to go and look up man
pages too. I spend hours brute forcing every possible combination of single and
double quotes and escaping and double-escaping every character in my regular
expressions until I get something that looks like abstract ASCII art, all while
trying to remember the difference between
perl regular expressions.
Bitbucket recently released a new add-on module type: the FileView. FileViews allow you to define how files of a particular type are displayed on the Bitbucket source view page. In this post, I'll show you how I built Run, Bucket, Run: a fun, if somewhat inefficient, way to view your source.
A few weeks ago, we introduced Atlassian Connect for Bitbucket, an add-on framework that lets you modify the Bitbucket UI. This post is a quick walkthrough on how to build a simple add-on that retrieves data from a repository, does some simple aggregation and displays it to the user.
A few weeks ago, a "vulnerability" was discovered in a new security feature that shipped in Git 2.2.0: signed pushes. No need to panic though! It is vanishingly unlikely that anyone would be able to successfully exploit this particular problem. In fact, the issue was quietly fixed a few days ago in the 2.3.7 point release.
We have all been there. When we started bitHound I knew we would inevitably be supporting multiple platforms and different environments for analyzing code. However, with several code hosting platforms out there and limited resources available we had to grab one platform to start and do so quickly.
It's that time of year again! Time for Atlassian's San Francisco office to be insanely jealous of our counterparts down under. Specifically, we're jealous of the Sydney office's graduate program: the Atlassian HackHouse.
If you're using Git, you're probably using pull requests. They've been around in
some form or other since the dawn of DVCS. Back before Bitbucket and GitHub
built fancy web UIs, a pull request might've simply been an email from Alice
asking you to pull some changes from her repo. If that sounded like a good
idea, you could run a few commands to pull the changes into your
git merge-distinct is a little tool that merges
multiple branches containing non-conflicting changes into a single head, using
octopus-merge strategy. Why would you want such a thing? Because while
it's useful to develop in the isolation of a feature branch, it can often be
useful to combine branches together for testing or deployment to a staging
One of my favorite Stash features is its plugin system. Since Stash is a git repository host, 99% of Stash users are software developers. And since developers often like to scratch their own itch, we've invested heavily in extensibility and customization to make plugins both powerful and simple to write. In this 30 minute video tutorial, I'll walk you through building, deploying and debugging a simple repository hook plugin, from scratch.
A critical vulnerability was identified in Git last week. This has been fixed in all maintained versions of Git (v18.104.22.168, v1.9.5, v2.0.5, v2.1.4, and v2.2.1) so upgrading is the best way to protect yourself. However a sensible second step is to secure your Git hosting server, so that pushes containing malicious trees are automatically rejected. This will prevent attackers from exploiting users who have yet to upgrade their local versions of Git.
A couple of weeks ago I ran a webinar on how to enhance your Git development experience with JIRA and Stash. The half-hour allocated for Q&A wasn't quite long enough, so I'm following up on some of the unanswered questions in blog form.
We've just completed another round of the Getting Git Right tour, spreading the love about the hottest DVCS across ten cities in North America and Europe. To cap off the tour, the presenters are getting together for a special Google Hangout to talk about developer workflow and the latest happenings in the world of Git.
After a few short months git 2.2.0 has been declared final. This is big news, as it comes with a host of new useful features for improving your git workflow. Here's the stuff we found useful at Atlassian: