ibuchanan

+1 for "Individuals and interactions over processes and tools"

That's correct. Bitbucket Pipelines uses Docker as an execution environment for builds. However, if the goal of your build is to produce a container, whether Docker or otherwise, Bitbucket Pipelines cannot do that at this time.

My colleagues have pointed out the simple answer is: Anything you can do with Bash, you can do in Bitbucket Pipelines.

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

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.

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.

Not so much. One of the things that I think makes Pipelines better suited for cloud is that it's agent-less. But that does mean there's no option to run an agent on-premise to bridge pipeline execution. Indeed, if you are accustomed to Bamboo, you are likely to find Bitbucket Pipelines rather minimalist. For example, there is currently no facility for aggregating test results.

Yes. You can run any test framework that runs inside a Docker container. And you can specify different "steps" for different branches (either by name or by globbing).

I'm one of the Developer Advocates at Atlassian with a focus on the CI/CD space.

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.