With the release of Bitbucket Pipelines into production this week (Blog Post Here), Atlassian looks like it has created a whole new set of “Bitbucket Cloud” pricing and packaging which incorporates a lot more than than just source code management. It’s not live yet but they plan to introduce soon. When? At the moment they are saying early 2017 and will give users 30 days notice.
Will you pay more? YES. It appears that pretty much everyone will pay more. For 10 Users on their Standard Plan you will pay $20/month whereas currently you pay $10/month. ($2 vs $1 per user). Should you be angry? NO. No one likes price increases but I think you can be “satisfied” and happy with this price increase. Here’s 2 reasons why:
On top of the Standard plan they are also introducing a Premium Plan for $5/user that gives you:
Will Bitbucket Cloud have a FREE Tier? YES. Bitbucket will still be free for up to 5 users, with unlimited public and private repositories. They give you 1 GB file storage and 50 build minutes for Pipelines per account per month.
Is “Unlimited” storage going? YES, it appears so. For as long as I can remember Bitbucket offered Unlimited Storage with some terms that covered abuse and also a fantastic guideline of keeping your Git repos smaller than 1GB. Now each plan tier has a storage limit with each subscription. At the moment the Premium plan comes with a 10GB storage limit. While this is a a lot for code repos, For any large development organization (100+ Users), they are going to run into issues here. I’m sure they will add “purchase additional storage” soon after launch or move to a model like Amazon, Cloudforge etc, where when you add users, you get additional storage.
Although in saying this, it also looks like they have brought Git Large File Storage (LFS) out of BETA, which will allow you to store large files remotely, keeping your code repo small.
To support the introduction of Bitbucket Pipelines, there will be add-on “Build Minutes” packages you can buy.
To view there upcoming pricing page – Click Here
Atlassian recently added a page where they compare their Bitbucket offering to GitHub. They compare the two offerings based on price and functionality. As well as highlighting their functional strengths, they do acknowledge where GitHub has functionality they don’t.
GitHub offers functionality such as side-by-side diff comments and code search that Bitbucket Cloud does not. We are currently working on bringing support for code search to Bitbucket Cloud. [Updated October 2016]
GitHub offers functionality such as full side-by-side diff, code search and Git Large File Storage (LFS) support that Bitbucket Cloud does not. We are currently working on bringing support for code search and Git LFS to Bitbucket Cloud.
Bitbucket vs GitHub Pricing Comparison
Source: Atlassian Bitbucket – Bitbucket Cloud vs. GitHub
Bitbucket vs GitHub Feature Comparison
[Updated October 2016] – Old Comparison Chart from June 2016
Today Atlassian is now offering a new continuous delivery feature within Bitbucket called Pipelines (BETA). It allows developers to now manage the development workflow, build, test, and deploy, all from within Bitbucket.
Check out this video overview from Atlassian:
This feature is currently in BETA. It looks like you can sign up to the BETA from the Pipelines feature page. Also, as there feature is in BETA, there is no information I can find as to how much it will cost and leaves open the following pricing and packaging questions for post BETA:
If you have had a chance to use it, please leave a review in the comments section below.
To learn more about Pipelines check out:
To put it in Atlassian marketing speak, it will “empower every team to accelerate their releases”. (‘Empower’….really? 🙂 )
Image Source: Atlassian
For the first time in years, GitHub has made changes to their pricing and packaging.
Historically GitHub has provided users with the ability to have unlimited public repositories, unlimited users, however have restricted the number of private repositories for paid plans (basically priced per private repository). Now GitHub has switched to a price per user model and unlimited private repositories, which is more aligned to the way people have been used to consuming other Git Hosting Solutions and other SaaS dev tools out there on the Market.
GitHub’s New Pricing Plans
You will also notice they have done away with the Personal ‘Micro’, ‘Small’, ‘Medium’, ‘Large’ plans and the Organization ‘Bronze’, ‘Silver’, ‘Gold’, ‘Platinum’ plans. If you are an Enterprise customer you will notice they are now ‘marketing’ the plan at $21 per user/month as opposed to $2500/year for 10 users. At first glance, it is definitely looks more appealing, however it is actually a price increase of approximately $0.17 per user/month (That’s an extra $20.40 per year!!)
I think for the first time GiHub’s pricing has got simpler and easier to compare to other git hosting providers.
Note: Free Accounts still only have unlimited public repositories.
GitHub’s Old Pricing Plans
Image Source: GitHub
Last month Unfuddle posted a blog talking about there 10 year history and announced a new product codenamed Unfuddle TEN that would be coming later in the year. Last week they posted a new Blog post with some more information and what UnFuddle TEN will incorporate based on customer feedback. The thing that caught Compare Git Hosting’s attention was the section on “Cost”:
Cost. You want free. And we have heard you. Unfuddle TEN is going to be free for personal accounts. Of course, we are going to save some of the fun for our paid accounts, but I think you will be very pleased to find that you can do most personal projects in Unfuddle TEN without paying a dime.
As to when Unfuddle TEN will be released and the Free edition be available, there is no mention. They say they will be releasing more of the roadmap in the coming weeks. Do you know more? Share in the comments below. Maybe they will align with their 10th anniversary in late June?
For more Information:
In November last year, Amazon Web Services announced their Git repository hosting service, CodeCommit at AWS re:invent. It the last week they have now made it generally available (you can pay for it!).
CodeCommit comes with a very generous Free Git Hosting offering before you start paying. (Unlimited Repos, 5 Users, 50GB Storage!). However, even when you have to pay for it, it’s only $1 per user! That’s very good value considering you get an extra 10GB storage per user.
It appears unlike most “AWS Free Tier” offerings that “AWS CodeCommit is available to both new and existing AWS customers indefinitely, and does not expire at the end of the standard 12 month Free Tier term.”
I have not had a chance to use the service and explore all it’s features yet. If you have, please lets us know in the comments section below what you think.
You can learn more here also:
Image Source: Amazon Web Services
On June 17th, Code Spaces was destroyed by a hacker who got access to their AWS Console. It looks like they are going to be shutting down for good.
“Code Spaces will not be able to operate beyond this point, the cost of resolving this issue to date and the expected cost of refunding customers who have been left without the service they paid for will put Code Spaces in a irreversible position both financially and in terms of on going credibility.
As such at this point in time we have no alternative but to cease trading and concentrate on supporting our affected customers in exporting any remaining data they have left with us.”
Code Spaces Website notice:
Code Spaces : Is Down!
On Tuesday the 17th of June 2014 we received a well orchestrated DDOS against our servers, this happens quite often and we normally overcome them in a way that is transparent to the Code Spaces community. On this occasion however the DDOS was just the start.
An unauthorised person who at this point who is still unknown (All we can say is that we have no reason to think its anyone who is or was employed with Code Spaces) had gained access to our Amazon EC2 control panel and had left a number of messages for us to contact them using a hotmail address
Reaching out to the address started a chain of events that revolved arount the person trying to extort a large fee in order to resolve the DDOS.
Upon realisation that somebody had access to our control panel we started to investigate how access had been gained and what access that person had to the data in our systems, it became clear that so far no machine access had been achieved due to the intruder not having our Private Keys.
At this point we took action to take control back of our panel by changing passwords, however the intruder had prepared for this and had already created a number of backup logins to the panel and upon seeing us make the attempted recovery of the account he proceeded to randomly delete artifacts from the panel. We finally managed to get our panel access back but not before he had removed all EBS snapshots, S3 buckets, all AMI's, some EBS instances and several machine instances.
In summary, most of our data, backups, machine configurations and offsite backups were either partially or completely deleted.
This took place over a 12 hour period which I have condensed into this very brief explanation, which I will elaborate on more once we have managed our customers needs.
All svn repositories that had the following url structure have been deleted from our live EBS's and all backups and snapshots have been deleted:
All Svn repositoies using the following url format are still available for export but all backups and snapshots have been deleted:
All Git repositories are available for export but all backups and snapshots have been deleted
All Code Spaces machines have been deleted except some old svn nodes and one git node.
All EBS volumes containing database files have been deleted as have all snapshots and backups.
Code Spaces Status
Code Spaces will not be able to operate beyond this point, the cost of resolving this issue to date and the expected cost of refunding customers who have been left without the service they paid for will put Code Spaces in a irreversible position both financially and in terms of on going credibility.
As such at this point in time we have no alternative but to cease trading and concentrate on supporting our affected customers in exporting any remaining data they have left with us.
All that we can say at this point is how sorry we are to both our customers and to the people who make a living at Code Spaces for the chain of events that lead us here.
In order to get any remaining data exported please email us at support[at]codespaces.com with your account url and we will endeavour to process the request as soon as possible.
On behalf of everyone at Code Spaces, please accept our sincere apologies for the inconvenience this has caused to you, and ask for your understanding during this time! We hope that one day we will be able to and reinstate the service and credibility that Code Spaces once had!