On Codeship, you are able to define deployment pipelines. A deployment pipeline is bound to a branch. Every time you push a new commit or tag to this branch, you trigger a build for it and the build will kick off your deployment pipeline.
You can add multiple deployments within one deployment pipeline. This way you can, for example, deploy to a staging environment first and, if that succeeds, follow up with a deployment to the production environment. This process is fully automated on Codeship and in case of errors you will get notified immediately. It is not possible to run multiple deployments in parallel.
Go to the Deployment page of your project settings to set up your deployment.
Add a branch that you would like to deploy and save it.
Choose your hosting provider or deployment method.
Fill out the deployment configuration and click the green checkmark on the top right of your deployment to save it.
On the next push to this branch (in this case ‘master’) the deployment will be triggered under the condition that all setup and test commands pass successfully.
Now you can add additional deployments or configure another deployment pipeline.
You can add multiple deployments to one deployment pipeline. They will run sequentially and can be ordered by dragging the deployment symbol.
If you want to create a deployment pipeline for another branch, click on “Add a branch to deploy” and enter the branch name.
After saving the deployment pipeline you can add your deployment methods for that branch.
Note: you can also use a wildcard branch to setup one deployment pipeline to be used for similar branches, e.g. feature branches. See Wildcard Deployments for more details on using wildcard branches.
By clicking on “Edit Branch Settings” you can change the branch name or delete that branch.
You can use the Script Deployment to run your custom deployment commands or to execute other tasks right after or before a deployment.