Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Codeship vs Cruise Control, the Slant community recommends Codeship for most people. In the question“What are the best continuous integration tools?” Codeship is ranked 3rd while Cruise Control is ranked 33rd. The most important reason people chose Codeship is:
Support for public and private GitHub and BitBucket repositories. It also has support for multi-user teams.
Specs
Question Ranking
Pros
Pro GitHub & Bitbucket integration
Support for public and private GitHub and BitBucket repositories. It also has support for multi-user teams.
Pro Keeps it simple. Doesn't allow too many "tricky" things which means builds are generally very stable once they are up and going.
Pro Headless browser support
Alongside latest Chrome and Firefox, Codeship supports the use of Selenium, PhantomJS, CasperJS as well as tools like Capybara.
Pro Build status GIF
There's a continuously updated GIF of the build status of the repository allowing you to determine whether build was successful or not.
Pro Support for multiple tools, languages and databases
Support for e-mail, HipChat, Slack, Campfire, Flowdock, Grove, Webhook, Github Status API.
Support for Ruby, Python, Node, Dart, PHP, Java, Scala, Groovy, Clojure, Go.
Support for: PostgreSQL, MySQL, MongoDB, Redis, Memcached, ElasticSearch, SQLite.
Pro Supports 7 cloud providers
Support for AWS, Digital Ocean, Rackspace, Google Compute, Joyent, Softlayer, Openstack.
Pro Docker support
Pro Simple deployments with a choice of 5 deployment tools
Support for Capistrano, Fabric, Chef, Puppet, Ansible and allows for writing your own scripts to deploy and manage your infrastructure.
Pro Supports 10 hosting providers
Support for Heroku, Engine Yard, Nodejitsu, dotCloud, App Engine, AppFog, Modulus, Openshift, Cloud Foundry, Fortrabbit and you can also run your own script to deploy anywhere.
Pro FTP, SFTP, SCP, RSYNC and SSH support
You can use FTP, SFTP, SCP, RSYNC and SSH for Continuous Deployment.
Pro Code Climate & Coveralls support
Automated code review for RoR and JavaScript and test coverage history and statistics with Code Climate and Coveralls.
Pro .NET version
Cruise Control .NET can be used on Windows to build .NET applications, although it is dated by now, it still can be interesting for use on low-spec systems.
https://sourceforge.net/projects/ccnet/
Pro Free and open source
Cruise Control is a free and open source project built with Java and hosted on Sourceforge.
Cons
Con Doesn't support git modules
If repo contain private submodule - build will fail, no way to add your private key.
Con Any time you ask support for help on Codeship basic (which isn't free anyway), they will just try to up sell you to Pro version.
Con No Global variables that can be shared amongst all projects.
Con Environment variables are exposed. Any keys or secrets can just be copied.
No option to mask them unless you reduce permissions for those users. Developers need to be able to modify a job but probably shouldn't be able to copy a production api key. Just needs one more level of permissions here.
Con Too many permissions on Bitbucket
When registering with Bitbucket Codeship it requests way to many permissions, even "Read and write to your team's projects and move repositories between them". Before giving all these permissions you have to be sure you can trust this service.
Con A bit tricky to set up
CruiseControl may be a bit tricky to set up. However, it has been around for quite a while so it should be pretty easy to find resources to help you out.
