Codeship is a handy little cross-platform CI/CD tool
We use Codeship to manage our deployment and continuous integration pipelines across different environments, version control hosts, and …
CloudBees Codeship
CloudBees Codeship
Overview
Recent Reviews
Reviewer Pros & Cons
View all pros & cons
Video Reviews
Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of CloudBees Codeship, and make your voice heard!
Pricing
View all pricingN/A
Unavailable
What is CloudBees Codeship?
Codeship from CloudBees is a build automation platform from the Austrian company of the same name.
Entry-level set up fee?
- No setup fee
For the latest information on pricing, visithttps://codeship.com/pricing
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting / Integration Services
Would you like us to let the vendor know that you want pricing?
1 person want pricing too
Alternatives Pricing
What is CircleCI?
CircleCI in San Francisco offers an eponymous build automation platform.
What is Azure DevOps Services?
Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
Features Scorecard
No scorecards have been submitted for this product yet.Start a Scorecard.
Product Details
What is CloudBees Codeship?
CloudBees Codeship is a hosted Continuous Integration and Delivery platform. It sits between a source code repository (e.g. GitHub, GitLab or Bitbucket) and the hosting environment (e.g. Amazon Web Services) and automatically tests and deploys every change in your platform. The product aims to allow Engineering teams to focus on developing better applications instead of wasting time on maintaining a cumbersome CI server. According to the vendor, Codeship scales with the user's needs, and allows users to speed up test suites and enables developers to ship better code faster.
CloudBees Codeship Screenshots
CloudBees Codeship Videos
An Introduction to Codeship Basic
An Introduction to Codeship Pro
CloudBees Codeship Integrations
CloudBees Codeship Competitors
CloudBees Codeship Technical Details
| Deployment Types | SaaS |
|---|---|
| Operating Systems | Unspecified |
| Mobile Application | No |
| Supported Languages | English |
Comparisons
View all alternatives
Frequently Asked Questions
What is CloudBees Codeship?
Codeship from CloudBees is a build automation platform from the Austrian company of the same name.
What are CloudBees Codeship's top competitors?
Who uses CloudBees Codeship?
The most common users of CloudBees Codeship are from Small Businesses (1-50 employees) and the Information Technology & Services industry.
Reviews and Ratings
 (11)
Reviews
(1-6 of 6)- Popular Filters
Companies can't remove reviews or game the system. Here's why
August 15, 2021
Codeship is a handy little cross-platform CI/CD tool
We use Codeship to manage our deployment and continuous integration pipelines across different environments, version control hosts, and technology stacks. We have implemented CI/CD workflows for various clients using Codeship, and its versatility in being able to handle different cloud environments such as AWS, Azure, GCP, and even plain old on-prem servers has made it an invaluable tool that can be applied to all requirements. The fact that it is a managed service on the cloud removes the headache of having to maintain our own instance of it.
- Inter-cloud deployments
- Integration with different version control providers
- Easy-to-use UI
- Quick configuration
- Better capabilities for deploying CI/CD pipelines as code
- Better support for enterprise-grade customers
- Better logical grouping capability for projects
November 15, 2018
Review of Codeship from the perspective of overall reliability in a small development team
At our company we use Codeship as part of our suite of devops tools to deliver web sites/apps to our various cloud servers. It has helped significantly streamline and speed up our deployment process to any of our clients' servers for development, staging, and actual production servers.
- Codeship provides a set of tools for quickly creating and building our deployment artifacts and push them to the designated servers.
- Codeship's hooks allows our developers to simply push tags from our git repositories to initiate a deployment of code to a server. No one outside of the devops team needs any expertise to get our code packages delivered.
- Codeship allows us to tie in behat and unit tests easily to prevent delivery of buggy code.
- The only real gripe I have with Codeship is with regards to its single sign-on experience within the website. Occasionally I accidentally try to sign in with my GitHub account instead of my Bitbucket account. By the time I realize the error, it is stuck in a transition state that it does not let me "sign out of". This is fixed by clearing cookies, but it would be nice to see some sort of sign out option before you are fully signed in.
April 10, 2018
Why we use Codeship
We use Codeship for most new projects, if we want to have a quick process to deploy from our version control system to staging or production environments. Codeship setup is quick and part of our common project bootstrap process: you can say that a project is correctly setup, if we can push code and have an updated infrastructure a few minutes later.
- Quick setup for continuous integration: push to a specific branch and run deployment scripts to see updates on the corresponding environment
- We can quickly see if there is something wrong: whenever we make changes, Codeship runs the whole build and then tests the code before deploying to production. The default setting is to run build and test on all branches, so there is usually no feature branch with a red build that we are not aware of
- Deployment scripts are very easy to configure and with the limited (but powerful) setup options, we usually have a clear process that describes the deployment. This way everything is clear, even for engineers new to the project.
- I would like to see a little bit more than the green/red status. If there are tests, it would be good to see how many have failed on a red build.
- To improve build times (and reduce feedback times), it would be good to see how long build, tests, and deployment take over time. An overview like that could very easily point to potential areas of improvement. I think Codeship users do not want to bother with the build process, but, if there is anything to improve and increase productivity it's very unlikely that users wouldn't want to do this.
March 30, 2017
Life is easer with Codeship!
I'm using Codeship for continuous integration and deployment of my personal front end and node projects. Codeship integrates great with Bitbucket and GitHub. It's saves a lot of time with deploys and tests.
- Easy and fast deployment
- A lot of tool integrations (Slack, GitHub, Bitbucket, GitLab)
- Getting tests to run is fast and easy
- Copeship is an external service, I can't install it inside our company's private network
- I can't use it for free for my private repos
- No open source support
December 09, 2016
Since we started using Codeship our deployments are more faster.
Basically we use Codeship for continuous deployment automation of our main public website and other internal web applications. Codeship is used by our IT department to ensure our code is reliable before sending it to production.
- Pretty easy to set up.
- Great documentation.
- Can be integrated with top tech companies.
- User Interface.
December 08, 2016
Simple and Intuitive Tool for Continuous Delivery
Codeship is used for simple CI and CD strategies for our small research and development projects. Whenever a new research project is 'bootstrapped' we instantly launch a git repository along with a codeship instance for the project thereof. There, we create our strategies for making sure our acceptance and functional tests are run before the code gets shipped onto production or onto a staging server. It's solely used by our development department, specifically by those involved in the research and development tasks.
- Build Automation: It's no longer necessary to run many other tools along with the git push command.
- Continuous Integration: We were finally able to achieve K.I.S.S. [keep it simple, stupid] methodology at our development environment.
- Continuous Deployment: If everything looks good, it no longer needs to be sitting there, waiting for some other bureaucratic task sequence to be run in order to get deployed.
- 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.