90 Reviews and Ratings
11 Reviews and Ratings
If you value integration over cost, Bamboo is clearly the way to go. It offers tight integration to the rest of the Atlassian suite, and when you need traceability from issue to build, Atlassian is the right way to go. However, if you find yourself needing to save on costs, you may consider taking an approach of rolling your own build system with open source alternatives, such as Jenkins, if you don't [mind] putting in a little extra elbow grease.Incentivized
Codeship is extremely well suited for projects that are version controlled on public hosting such as Github or Bitbucket, and for situations where you need to pick up code from these systems and deploy it to different cloud environments. For example, we had two projects for the same client that were hosted on Github and needed to be deployed to AWS and Heroku. The native CI/CD tools of these cloud environments could not provide a holistic solution to deploy to both environments the way Codeship did.Incentivized
Levels of granularity. Organization has many projects that have many build plans that have many jobs that have many tasks, etc. And branch builds allow source control branches to be built separately.Versatility. I can use bamboo to manage my Java, node, or .NET build plans. I can use it to spin up Windows or Linux build agents, or install it on a Mac to build there as well.Bamboo integrates with other Atlassian products like Bitbucket, Stash, JIRA, etc. If a company commits to the entire Atlassian stack then work can be tracked through the whole development lifecycle which is really useful.Incentivized
Codeship provides a set of tools for quickly creating and building our deployment artifacts and push them to the designated servers.Codeship's hooks allows our developers to simply push tags from our git repositories to initiate a deployment of code to a server. No one outside of the devops team needs any expertise to get our code packages delivered.Codeship allows us to tie in behat and unit tests easily to prevent delivery of buggy code.Incentivized
Extremely hard barrier to entry for non-backend developersBlackbox makes it hard to customize functionalityThe inability to add features without breaking core functionalityNo cloud solutionTasks cannot be put in if/else statementsNo clear right way to form build plansIncentivized
I would like to see a little bit more than the green/red status. If there are tests, it would be good to see how many have failed on a red build.To improve build times (and reduce feedback times), it would be good to see how long build, tests, and deployment take over time. An overview like that could very easily point to potential areas of improvement. I think Codeship users do not want to bother with the build process, but, if there is anything to improve and increase productivity it's very unlikely that users wouldn't want to do this.
Bamboo was fairly easy to navigate but in the end it always felt as if it was developed as a bolt-on and not a true group up user interface. There were multiple ways to get to everything and the path was never the same. So it was difficult for users to really get a feel of how to use the application.
Support for Bamboo has started lack a little over the years. Atlassian has been moving more towards Bitbucket Pipelines and away from the on-premise install of Bamboo. While the tool is still great, it may take a little bit of time to get a question answered by official support.
We selected Bamboo because its capabilities to integrate with other Atlassian products specially Jira Software, Bitbucket and in some useful scenarios with Confluence. Also, we found these pros important for us: great user interface, easily agent deployment, Docker compability, simply to maintain / manage, and straightforwardly integration with different notification platforms Incentivized
Our company uses Jenkins for all internal deployment processes for one very important reason - it's hosted internally. But Codeship is great for personal use - it has intuitive UI, easy setup and tons of integrations.Incentivized
It helped us achieve the Continuous Deployment and Continuous Integration goals for our applications, a huge milestone that saved a lot of time for developers in making the builds and deployments and saved time for QA in running the automated tests.Helped with DevOps: we moved the formal approval from the email to the system and allowed the approver to actually push the button for the production deployments.Biggest positive impact of using Bamboo is that it improved our response time to customers and increased the frequency of our deliveries to them.Incentivized
Having the code tested thoroughly. While it's obviously a part of the job that still requires the developer to sit down and to actually have some decent and thorough tests implemented, by using codeship we were able to guarantee 100% that our code was being tested each and every time it got commited and pushed onto our repositories. Leading to a faster, shorter and sure implementation iterative cycle.Fewer 'man in the middle' processes which required more steps and people involved just to get the code shipped onto our deployment servers.Almost inexistent learning curve. Codeship is simple to use and very intuitive. Nobody in our development department had a hard time figuring out how to have it properly configured for each new project created there.Incentivized