ibuchanan

3 ms·

1.
by ibuchanan 10y ago
+1 for "Individuals and interactions over processes and tools"
2.
by ibuchanan 10y ago
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.
3.
by ibuchanan 10y ago
My colleagues have pointed out the simple answer is: Anything you can do with Bash, you can do in Bitbucket Pipelines.
4.
by ibuchanan 10y ago
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 c
5.
by ibuchanan 10y ago
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
6.
by ibuchanan 10y ago
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 e
7.
by ibuchanan 10y ago
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 accustom
8.
by ibuchanan 10y ago
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).
9.
by ibuchanan 10y ago
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