3 ms·

(Disclaimer; I'm an Atlassian employee.) Bamboo is still the recommended solution for on-premises installations. The requirements and practicalities of OP vs c

(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-integration http://summit.atlassian.com/videos/build/docker-continuous-i...

blktiger 10y ago
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.
- stuff4ben 10y ago
  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-bitbucket-pipelines-yml-792298910.html https://confluence.atlassian.com/bitbucket/configure-bitbuck...
  - blktiger 10y ago
    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.
- itomato 10y ago
  You're not alone: https://jira.atlassian.com/browse/BAM-1223 https://jira.atlassian.com/browse/BAM-1223 Dear Atlassian: This request has now been open for 9 years and has 247 votes. 9 years.

blktiger 10y ago

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.

stuff4ben 10y ago
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-bitbucket-pipelines-yml-792298910.html https://confluence.atlassian.com/bitbucket/configure-bitbuck...
- blktiger 10y ago
  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.
itomato 10y ago
You're not alone: https://jira.atlassian.com/browse/BAM-1223 https://jira.atlassian.com/browse/BAM-1223 Dear Atlassian: This request has now been open for 9 years and has 247 votes. 9 years.