Bitbucket Pipelines Beta: continuous delivery inside Bitbucket(blog.bitbucket.org) |
Bitbucket Pipelines Beta: continuous delivery inside Bitbucket(blog.bitbucket.org) |
Coming from a non-microsoft background (github + jenkins + travisci) I have been pleasantly surprised. Full disclosure, I currently work at M$.
http://blog.npmjs.org/post/144855273708/announcing-npm-for-a...
I was really impressed; It's really slick having the source-control/collaboration and CI/CD so tightly integrated.
At this point, the only thing keeping me on BitBucket instead of GitLab is Mercurial support.
Have used both, they are so close, seems "odd" to go for the way less popular one, barring you have a really old HG repo and haven't bothered to switch.
Mercurial has a number of features that git never implemented - in particular revsets. I also prefer the hg CLI over the git CLI. Mercurial has sane, concise online help, and a lot of work went into the design of the command-line to be consistent, composable, and made of pieces that do one thing and do it well.
But, I'll grant its not worth fighting over if I am working with collaborators who have a git preference.
We've always been invested in the CI/CD market (Bamboo has been around a long time) and Pipelines was just making sense for us to do to help all Cloud teams to build great software.
Sten, Bitbucket Pipelines Product Manager
Congrats on the beta launch, the more competition there is, the better for everybody!
For "old-fashioned on-premise" CI/CD, Bamboo Server is still a solid offering from Atlassian, with active development on new features and support for existing ones. Discontinuing Bamboo Cloud is more about being able to "right-size" our cloud offerings so Atlassian can offer a CI/CD service for a team's first microservice deployed into AWS Elastic Beanstalk, and that scales up without overhead to many services each with many instances in a more complex environment like AWS ECS. And not just for AWS but for Azure, Google, Heroku, or whatever your choice of cloud platform. I believe Bitbucket Pipelines will be that next generation solution, while Bamboo will continue to serve on-premise needs for many years to come.
With Bamboo Cloud you were able to set up a pretty convenient "intermediate" solution, with Bamboo Cloud + an agent on your servers. Will it still be possible with Pipelines?
Also I couldn't find the doc for aggregating tests results.
[1] https://confluence.atlassian.com/pages/viewpage.action?pageI...
Bamboo is still the recommended solution for on-premises installations. The requirements and practicalities of OP vs cloud CI are different enough that they warrent different approaches.
That said, Bamboo supports scaling builds using AWS, and has 1st-class support for Docker-based build/test setups. I gave a talk on this at Atlassian's Summit last year if this sounds useful: http://summit.atlassian.com/videos/build/docker-continuous-i...
It's saying 'Sorry, that post was not found.'
This doesn't help improve my confident in Bitbucket, which is already pretty low based on past uptime: https://statusgator.com/services/bitbucket
I can only with for support of FreeBSD/Jails.
[1] https://www.youtube.com/watch?time_continue=122&v=p5KgjeZB8W...
[1] https://confluence.atlassian.com/display/BITBUCKET/Bitbucket...
I'm one of the Product Manager on Bitbucket Pipelines. The beta is indeed free, with a limitation on the number of minutes per user per month (starting at 300mins/user/month but that may change during the beta).
We haven't decided on the post-beta pricing yet. The beta will help us understand better how our customers are using it so that we can price it accordingly. We're leaning towards a model that scales well with the number of users on an account.
Let me know if that helps.
Thanks,
Sten Pittet
Some of the ideas we're working on to improve it further:
- deployment environments (acceptance, pre-prod, prod)
- manually confirming deployments for production
- review apps deployments of feature branches
So, the first thing to check is for simple REST APIs that you can curl. If I recall correctly, GAE is tricky because it takes more than 1 API call.
Next, check for a CLI or script library. I see Google provides an SDK that might work: https://cloud.google.com/appengine/downloads#Google_App_Engi...
In that case, we have to pull the library into an appropriate image. For example, here's how the Amazon folks solved for S3: https://bitbucket.org/awslabs/amazon-s3-bitbucket-pipelines-...
I won't have time to look at GAE more closely until next week, but hit me up on Twitter if you want to DM me: @devpartisan
https://github.com/GoogleCloudPlatform/golang-samples/blob/m...
https://github.com/GoogleCloudPlatform/golang-samples/blob/m...
Those might be useful for configuring Bitbucket Pipelines.
Dear Atlassian: This request has now been open for 9 years and has 247 votes.
9 years.https://confluence.atlassian.com/bitbucket/configure-bitbuck...
[1] https://confluence.atlassian.com/pages/viewpage.action?pageI...
If I understand right the thing you're expected to provide to run inside "pipelines" is a container in which your build can be performed; the output of that build might also be a Docker container, but hopefully there is not a requirement that it be the same container in which you are performing the build. Or you might be shipping something completely different, totally unrelated to Docker, as your build output that gets sent onward to production. Of course all of this is just a guess, it will become more clear as some of us start to enter the beta program.