CloudBees Codeship vs. Continua CI

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

Incentivized

Mostly it is very suitable for any product based company who wants to add a CI system for their products. This tool is perfectly suitable for a company which releases builds very frequently. By using this tool they can reduce a tremendous amount of manual effort. If company's budget is not high and if they can not afford the premium plan then this tool won't be suitable for them because the basic version of this tool won't provide much functionality

Incentivized

• Easy and fast deployment
• A lot of tool integrations (Slack, GitHub, Bitbucket, GitLab)
• Getting tests to run is fast and easy

Incentivized

• First thing is this tool is scalable which is the biggest advantage of this tool. It won't take much time in setup and making it ready. It has a very good user interface.
• This tool has almost every source code repository support like Git, SVN, Microsoft Foundation Server etc. Moreover, it has very good support for various build tools like Visual Studio, MSBuild etc., which makes it even batter.
• We can trigger multiple builds at a time with the Premier subscription.
• It allows users to apply many deep levels of configurations which make the whole system even easier.

Incentivized

• UX: The overall UX is not bad, but it still needs a lot of improvement.
• It took me quite a while to realize that in order to switch projects I needed to press my current project name so a dropdown would appear.
• Integration with bitbucket is somewhat hidden from the users's hands. Got to make some improvements there.

Incentivized

• Mostly I don't have much more recommendation for improvement because this tool provides almost everything which would be required in any continuous integration system. But still I would suggest improvement in the reporting system. The build report is a field where they can make improvement by adding more information if they want.

Incentivized

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.

Incentivized

In my previous company I have used Jenkins for maintaining their CI system. Even this tool is also very good. The good thing about this tool is it’s an open source project. So in terms of pricing, we can consider this tool as an alternative to continua CI. One has to compare both of the products before going to use any one because both have their own benefits and drawbacks.

Incentivized

• 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.

• Basically, this tool will reduce manual effort of creating, deploying and testing software products. So ultimately it will reduce manpower which would otherwise be required for such things.
• It is time saving and improves the overall performance of the entire team and system.

Incentivized