Live data from Hacker News

Bitbucket Pipelines Beta: continuous delivery inside Bitbucket

blog.bitbucket.org

31–40 of 73 posts

Re: Bitbucket Pipelines Beta: continuous delivery inside Bitbucket

#31

Curious if there's going to be an on-prem version of this? We run Bitbucket at my company and Jenkins Enterprise as well. How does Bitbucket Pipeline compare to Jenkins Pipeline ( https://jenkins.io/solutions/pipeline/ )?

(Disclaimer; I'm an Atlassian employee.)

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...

Re: Bitbucket Pipelines Beta: continuous delivery inside Bitbucket

#33

What about multi-language repositories? If I have Java + Ruby, how will Pipelines work?

It uses Docker to manage the installed dependencies, so you can build your own Docker image with whatever you need and then use that in the pipeline configuration: https://confluence.atlassian.com/bitbucket/use-docker-images...

Re: Bitbucket Pipelines Beta: continuous delivery inside Bitbucket

#34

What about multi-language repositories? If I have Java + Ruby, how will Pipelines work?

It uses Docker to manage the installed dependencies, so you can build your own Docker image with whatever you need and then use that in the pipeline configuration: https://confluence.atlassian.com/bitbucket/use-docker-images...

You mean I should build a Docker image with both Java and Ruby? The image would be much larger than intended in that case. In production, I would have two different Docker images.

Re: Bitbucket Pipelines Beta: continuous delivery inside Bitbucket

#35

Earlier quoted context omitted.

It uses Docker to manage the installed dependencies, so you can build your own Docker image with whatever you need and then use that in the pipeline configuration: https://confluence.atlassian.com/bitbucket/use-docker-images...

You mean I should build a Docker image with both Java and Ruby? The image would be much larger than intended in that case. In production, I would have two different Docker images.

It is unfortunately common to ship Docker containers to production that contain the entire tooling suite to build the thing being deployed, and it sounds like that might be what is happening in your case?

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.

Re: Bitbucket Pipelines Beta: continuous delivery inside Bitbucket

#36

It's too bad this is git only for now. Is there any plan to add support for mercurial repositories?

Oh. Well shit. I signed up for the beta without realising this.

At this point, the only thing keeping me on BitBucket instead of GitLab is Mercurial support.

Re: Bitbucket Pipelines Beta: continuous delivery inside Bitbucket

#39

Earlier quoted context omitted.

It uses Docker to manage the installed dependencies, so you can build your own Docker image with whatever you need and then use that in the pipeline configuration: https://confluence.atlassian.com/bitbucket/use-docker-images...

You mean I should build a Docker image with both Java and Ruby? The image would be much larger than intended in that case. In production, I would have two different Docker images.

At this time, it is a limitation of the beta that Bitbucket Pipelines can only associate a single image with your build. Avoiding the complexity of chaining images helped us to ship more quickly. I expect this will change before GA. For now, you would have to effectively "merge" the Dockerfiles your self and publish the image so Bitbucket Pipelines can pull it.

Re: Bitbucket Pipelines Beta: continuous delivery inside Bitbucket

#40

Curious if there's going to be an on-prem version of this? We run Bitbucket at my company and Jenkins Enterprise as well. How does Bitbucket Pipeline compare to Jenkins Pipeline ( https://jenkins.io/solutions/pipeline/ )?

(Disclaimer; I'm an Atlassian employee.) 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:…

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 for deployments to prevent a hacker from using bamboo to access all the other servers.
Post reply on HN