Codeship from CloudBees is a build automation platform from the Austrian company of the same name.
N/A
CloudBees Continuous Integration
Score 7.8 out of 10
N/A
CloudBees Continuous Integration (formerly the CloudBees Jenkins Platform) is a continuous integration (CI) and continuous delivery (CD) solution that extends Jenkins. Developed for on-premise installations, CloudBees CI offers stable releases with monthly updates, as well as additional proprietary tools and enterprise features to enhance the manageability and security of Jenkins. CloudBees CI helps administrators manage growing installations due to ever-increasing teams, projects and jobs…
Codeship is easier to use than Jenkins because it does not require you to set up your own server, and it provides a large amount of out-of-the-box integrations for version control systems and cloud environments. AWS CodePipeline is native to AWS and cannot deploy applications …
Codeship has been easier for our devops team to work with as far as making delivery plans and build scripts. Anecdotally, it has been more stable over time, cutting down on time investigating why some random part of the delivery process has broken. I am not sure why this is, …
We have been using Codeship for a few years, and what we like is that it's very clear what is built and when. We usually only have one-liners for any configuration option (build, test, deploy) and this way all changes to the build are managed in the version control system and …
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.
Back in those days, we didn't know about Gitlab, and Bitbucket didn't provide a CI pipeline. Jenkins is just too much for the simple tasks we wanted to achieve, besides, we didn't have a dedicated server for the sole purpose of having our code pipelined though continuous …
Easy to lean, use, highly customizable pipelines, works well for version control, etc. Example Digital.ai gives all those features which can be done in Jenkins like builds, deployment, release management, etc. But, it requires universal templates to be created which are …
CloudBees Jenkins Support is on par with the other enterprise tools we're currently using. It has performed well enough that we've adopted the product and placed it in the critical path of our software delivery pipelines.
Codeship is very well suited to teams that have specialized devops members along with other specialized developers. It lets the other developers focus on what they do best, without having to learn another technology stack. This has cut down on a lot of headaches at our company with developers needing to deploy code to various different hosting services across different content management systems. The experience to push code is essentially the same for a developer no matter what the underlying technology is
If you're running Jenkins in your enterprise and it's in the critical path of your software pipelines, I highly recommend CloudBees Jenkins over the open source version of the product to ensure you've got the customer and technical support you'll need for your Jenkins platform to be successful.
Support seems very unreachable from my experience. They handle cases if developers are facing issues, support seems to be very limited. It's not like other tools in a market where every mail is being taken priority and responses are sent. We see a lack in this particular aspect when it comes to CloudBees Jenkins Platform.
Codeship is easier to use than Jenkins because it does not require you to set up your own server, and it provides a large amount of out-of-the-box integrations for version control systems and cloud environments. AWS CodePipeline is native to AWS and cannot deploy applications reliably to other cloud environments such as GCP or Azure.
Easy to lean, use, highly customizable pipelines, works well for version control, etc. Example Digital.ai gives all those features which can be done in Jenkins like builds, deployment, release management, etc. But, it requires universal templates to be created which are difficult to maintain and readable like groovy pipelines in Jenkins.
We have a few small projects with different developers and Codeship shows everyone clearly, if something work, or if it doesn't.
In one small project with a team of three developers, we have configured two builds and it takes 2-5 minutes for everyone on the team to push changes to an infrastructure handling a little over 3M users.