Live data from Hacker News

Bitbucket Pipelines Beta: continuous delivery inside Bitbucket

blog.bitbucket.org

71–73 of 73 posts

Re: Bitbucket Pipelines Beta: continuous delivery inside Bitbucket

#71
post #50
post #2

This is great. While I use only travis for build/testing at the moment, I really appreciate a real competition between GH / GL / BB. Users of all the platforms win because of this.

This is pretty much identical to how Gitlab does it. I was hoping they would take it at least one step further not just copy it.

[deleted]

Re: Bitbucket Pipelines Beta: continuous delivery inside Bitbucket

#72
post #9

Earlier quoted context omitted.

Hi, 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…

Do you have some details on the kind of hardware Bitbucket Pipelines will run, as that can affect the time it takes to run a workflow? More specifically, how many cores and how much memory will the containers have access to?

We will be experimenting different configurations during the beta to find the right fit. Some details about the resources available are published in our documentation [1] and will be updated as we move forward.

[1] https://confluence.atlassian.com/pages/viewpage.action?pageI...

Re: Bitbucket Pipelines Beta: continuous delivery inside Bitbucket

#73

Earlier quoted context omitted.

I really want a way to configure bamboo via a text configuration file though. We're using it now, but we have to copy the configuration from build job to build job and each job ends up subtly different over time. :( Plus I really want a way to say here are the steps to deploy to a server, now run those steps against these three servers. It would be even better if each server could potentially have it's own ssh key fo…

I think that's where Bitbucket Pipelines comes into play. Their YAML file is similar in concept to TravisCI and others. Jenkins Pipeline has a jenkinsfile which is also similar in concept but is based on Groovy. While there's a learning curve for that, I would argue it's definitely more powerful. https://confluence.atlassian.com/bitbucket/configure-bitbuck...

I'm not so sure about that, first off the pipelines feature doesn't exist on Bitbucket Server and Atlassian recommends you use Bamboo there. Secondly, that doesn't help with managing secure access to production servers with potentially sensitive data. You'd just be moving from storing all the passwords/ssh keys in bamboo to storing them all in your version control system.
Post reply on HN