CloudBees Codeship vs. HashiCorp Packer

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

We use packer to generate new machine images for multiple platforms on every change to our Configuration Management tools like Chef/Puppet/Ansible It's act single tool for Image building for Multi-provider like AWS/Azure/GCP Helps to achieve Dev/Prod Parity Packer itself doesn't have a state like Terraform. You can't do packer output AMI ID. If you have a scenario where you want to maintain the state for images it would be tough to manage via Packer.

Incentivized

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

Incentivized

• Multi-provider portability
• Greater testability
• Super fast infrastructure deployment

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

• Manageability
• Manageability
• Manageability

Incentivized

We are happy with the use of Packer in our organization. Apart from manageability, I don't find any other drawback with Packer.

Incentivized

It's best for building Image with many features and benefits.

Incentivized

I only once required support and it was very smooth.

Incentivized

I haven't found any issue in Implementation that itself describes how well this tool is built.

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

There are lot of tools in market which does the job for Image creation but all of them are not complete Machine/Image as a code. All other alternatives can create Image partially. Main reason for selecting Packer are Packer is lightweight, portable, and command-line driven Packer helps keep development, staging, and production as similar as possible. Packer automates the creation of any type of machine image Multi-provider portability is the feature to die for

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.

• Super fast infrastructure deployment
• Quick turnaround of infrastructure in multiple cloud using single tool.
• Increase productivity by reducing time in infrastructure building.

Incentivized