Based on the video, this appears to require Docker [1]
I can only with for support of FreeBSD/Jails.
[1] https://www.youtube.com/watch?time_continue=122&v=p5KgjeZB8W...
Bitbucket Pipelines Beta: continuous delivery inside Bitbucket
41–50 of 73 posts
Re: Bitbucket Pipelines Beta: continuous delivery inside Bitbucket
#42Earlier quoted context omitted.
While we don't have the "recipe" documented in an example repository, GAE does have right knobs and levers that would make it possible to use Bitbucket Pipelines with GAE. Give it a try! And, even if we haven't made an example repository yet, don't rule it out.
I'd love to, I just have no idea where I would even start. Any advice?
I've written some of the code for other deployment targets. One of my earliest was for S3: https://bitbucket.org/ian_buchanan/pipeline-example-aws-s3
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
Re: Bitbucket Pipelines Beta: continuous delivery inside Bitbucket
#43Yay, and once again us Google App Engine users are shafted from having good CD support, especially when we use Bitbucket as our repo host.
My colleagues have pointed out the simple answer is: Anything you can do with Bash, you can do in Bitbucket Pipelines.
Re: Bitbucket Pipelines Beta: continuous delivery inside Bitbucket
#44Earlier quoted context omitted.
(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 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...
Re: Bitbucket Pipelines Beta: continuous delivery inside Bitbucket
#45Earlier quoted context omitted.
(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 fo…
You're not alone: https://jira.atlassian.com/browse/BAM-1223
Dear Atlassian: This request has now been open for 9 years and has 247 votes.
9 years.Re: Bitbucket Pipelines Beta: continuous delivery inside Bitbucket
#46It's too bad this is git only for now. Is there any plan to add support for mercurial repositories?
Serious question... are you using HG because of history, or do people actively choose HG over Git for new projects still?
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.
Re: Bitbucket Pipelines Beta: continuous delivery inside Bitbucket
#47Earlier quoted context omitted.
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 ther…
Kyle, this is correct. We use containers simply to create the environment in which we'll execute the script commands in isolation. You can start with a small container and install dependencies during the run or you can prepare a bigger container with the dependencies installed already.
Re: Bitbucket Pipelines Beta: continuous delivery inside Bitbucket
#48This 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.
Don't forget VSTS either: https://www.visualstudio.com/products/visual-studio-team-ser...
Coming from a non-microsoft background (github + jenkins + travisci) I have been pleasantly surprised. Full disclosure, I currently work at M$.
Re: Bitbucket Pipelines Beta: continuous delivery inside Bitbucket
#49It's too bad this is git only for now. Is there any plan to add support for mercurial repositories?
Serious question... are you using HG because of history, or do people actively choose HG over Git for new projects still? 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.
I do, assuming its just for me. I still much prefer the hg cli over git.
But, I'll grant its not worth fighting over if I am working with collaborators who have a git preference.
Re: Bitbucket Pipelines Beta: continuous delivery inside Bitbucket
#50This 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.