CloudBees Codeship vs. TeamCode Tin

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

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

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

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

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