Last night, May 26th, the site was down for about 3 hours. This happened after midnight, European time, which means most of us were sleeping.
Our administrator, Mads Jørgensen, was attentive though, and had to endure long hours with coffee and disk resizing.
What happened: Late last night, we started getting errors saying “no space left on device.” True enough, the space had almost run out (well, the system reported 6gb free, but OK), and what we did to remedy this was to truncate a large logfile, and restart the services. Everything then went humming along, and we figured no one was going to push 8gb over night, and we’d deal with it early this morning.
Not so.
Just after I had gone to bed, allegedly things began acting up once more. Mads jumped to action, and replaced the front page with status updates. If you want to read just exactly what went wrong, and how he remedied it, you can read it on his blog:
http://swag.dk/bitbucket/downtime_27052009.html
Again, Mads, you saved the day, and we wouldn’t want to continue without you!
Posted in bitbucket.
We just deployed a minor design-change, specifically a new header. The main goal with the new header is to give a cleaner look, and save a few pixels vertically.
We also added a new “collapsed-mode” toggle at the bottom of the repository infobox:
If you click the arrow, you’ll hide a lot of the content in the infobox, stuff you’re probably not interested in seeing all the time anyway. Click the same arrow again to toggle back on.
Feedback is as always appreciated!
Posted in bitbucket, new stuff.
Ask, and you shall receive.
We’ve just unrolled a new feature on the site, Downloads. This lets you upload any file you want to your repository, be it public or private. The files are uploaded directly to Amazon S3, so our servers won’t even break a sweat.
After the upload is complete, your file will be accessible via the Cloudfront content delivery network (CDN), which allows for extremely fast downloads, all over the globe. If a repository is private, the URL for downloading a file will look a bit different (it will include an authentication token that is good for 24 hours), but that also means that your files are not accessible to anyone else, even if they have the full URL. For public files, they will be served from cdn.bitbucket.org/username/reponame/downloads/.
Files uploaded will count against your quota, but Mercurial repositories being notoriously small, you should have plenty of space, even on the free plan.
Some of our users have already begun upload, as can be seen here and here.
On another note, tags are now ordered by date instead of alphabetically.
A big thanks to Vetle Roeim for spending some time helping us out with this feature.
Posted in bitbucket, new stuff.
Some of you may have experienced mail showing up late, especially to @gmail.com addresses and Google groups.
This was caused by a missing SPF record for our mail server. One has been set up now, and those delays should be gone.
Read more about SPF (Sender Policy Framework) here.
Posted in bitbucket.
Well, it was inevitable. With the ever-growing popularity of Git, we figured we had to support it.
For several months now, we’ve been scratching our scalps, spending endless nights trying to wrap our heads around the inner workings of git. But in the end, it paid off, and we’re proud to announce:
We now support Git!
It took a while, but we feel confident we can provide an outstanding service to the community, and the barrier between hg and git is no more.
Some of our first git users are already emerging, go check them out.
Enjoy!
EDIT: This was an April fools joke, and we don’t now, nor will we any time soon support Git.
Posted in new stuff.
Tagged with git, hg.
Just this weekend we rolled out some exciting new changes, wiki-wize. 3 brand new things, actually!
1. /help/ is now a wiki
Yep. And it’s editable by anyone, so feel free to contribute! Anything you think might benefit others will do.
2. Wikis are globally editable
That means you no longer have to be a writer of a repository to be able to edit its wiki. All that is required is that you’re logged into Bitbucket.
Sounds kinda scary, but we’re trying it and we’ll see how it goes. Since you need an account, if anyone messes up your wiki, you can always see who it was.
3. The new “Table Of Contents” macro
This is something a lot of people have asked for, and we think we’ve delivered! The new macro allows you to generate a TOC for your page, but it goes way beyond that.
It can also generate TOCs for other files, or even a directory of files. On top of that, it takes an optional argument indicating how many header-levels it should include.
So <<toc>> works, but so does <<toc FAQ/>>, <<toc OtherPage/MaybeInSubDir>> and <<toc FAQ/ 2>>!
This is how we construct the FAQ section on http://bitbucket.org/help/.
The wiki there is itself a repository, so in case you want an offline copy, or your own fork, go for it.
Posted in new stuff, tips & tricks, wiki.
This has been requested by many users, and it’s finally live: issue editing.
Edit the title of an issue
As you can see underlined in the screenshot above, when you hover the title, a pencil-icon appears to indicate that the title is editable. Clicking the title allows you to make your changes:
Hit enter to save, and you’re done.
Edit the description of an issue
Also in the first screenshot, you can see an Edit-link underlined in the bottom right. Clicking this link lets you edit the description of the issue.
If you don’t see any of these Edit-links, that’s probably ok, you just don’t have access to editing all issues.
Edit an issue comment
After submitting a comment to an issue, you will have the possibility to edit your comment for 15 minutes. As you can see from the screenshot above, your time left with access to edit the comment will be shown and continuously updated.
That’s it, simple as that. Any questions or comments are more than welcome!
Feel free to join us on IRC, write a message to bitbucket-users on Google Groups, or report a bug or suggestion in our issue tracker.
Posted in bitbucket, new stuff.
We will be moving to a new, remarkably more powerful server park later tonight (GMT+1). If you can’t reach Bitbucket, do not fret, we expect the downtime to be around 10-15 minutes.
The move is to Amazon EC2, and from there it will be much, much easier to scale out due to the huge increase of traffic we’re seeing lately.
NB: There will also be a tiny bit of UI improvements after the move!
Posted in bitbucket, status.
By Eirik
January 12, 2009
Go to your repository’s admin-tab, and click “Appearance Settings” under “Additional options/settings”.
Here you can choose from a list of themes, and when switching theme in the dropdown the preview to the right will update immediately.
If you like dark themes, check out “Native”.
Posted in bitbucket, tips & tricks.
By Eirik
November 23, 2008
In your Bitbucket wiki-pages, you have access to data from the issue tracker through a set of wiki macros:
Link to a specific issue
Syntax: <<issue 1>> Result: A link to the issue with id 1 in your repository’s issue tracker.
Link to an issue query
Syntax: <<query ?status=open&status=new All open issues>> Result: A link to all issues with status open or new, where the link text is “All open issues”.
List all issues for a milestone (or show count)
Syntax: <<milestone Beta 1>> Result: A list of issues for milestone “Beta 1″, with links and status for each issue.
List all issues for a query
Syntax: <<issues ?status=open&status=new count|list|compact>> Result: Lists all issues that match the query (status is open or new) in one of two optional styles, or shows the number of issues that match the query.
<<issues ?status=open&status=new list>> shows a full list of open or new issues, in the same layout as the milestone-macro.
<<issues ?status=open&status=new compact>> shows a list of open or new issues, but only the issue id with a link to each issue in the tracker.
Usage example for count: “There are currently <<issues ?status=open&status=new count>> open issues for our project.”
Link to a changeset
Syntax: <<changeset 45cc878df717>> Result: A link to changeset 45cc878df717’s diff-view.
Posted in bitbucket, tips & tricks.
By Eirik
November 10, 2008
Latest comments