ContinuityApp

Create a Deploy Strategy

A Deploy Strategy identifies how to deploy a Project. As of today, a Project can be deployed only via Git push.

Auth&ACL

Both users and collaborators can access this API, via OAuth deploys scope (or HTTP Basic Authentication for development purposes).

Definition

POST https://v1.continuityapp.ws/projects/<project_id>/deploy_strategies

Arguments

Arguments    
name Required Human-friendly name of the test suite.
strategy_type Required Can be git. We are working to add more deploy handlers.

Deploy Strategy Specific Arguments

options:

Deploy Strategy options    
options[repository_url] Required The URL where git must push to. URL must be without protocol, eg: git@github.com:sinatra/sinatra.git
options[local_branch] Required The Git local branch to be pushed (eg: master)
options[remote_branch] Required The Git remote branch to push to (eg: master)

Example request

$ curl https://v1.continuityapp.ws/projects/123456789123456789/deploy_strategies?oauth_token=<access_token> \
    -d "name=heroku%20staging" \
    -d "strategy_type=git" \
    -d "options[repository_url]=ssh%3A%2F%2Fgit%40heroku.com%3Acontinuityapp-demo.git" \
    -d "options[local_branch]=master" \
    -d "options[remote_branch]=master" \
    -X POST

Returns

A deploy dependency object will be returned.

Example response

{
  "response": {
    "id": 123456789123456780,
    "id_str": "123456789123456780",
    "name": "heroku staging",
    "strategy_type": "git",
    "options": {
      "repository_url": "git@heroku.com:continuityapp-demo.git",
      "local_branch": "master",
      "remote_branch": "master"
    }
  }
}

Notes

Receiving repository must authorize ContinuityApp to push code there. To let the remote repository accept ContinuityApp pushes add your project SSH public key to the repository.

Errors

There are no specific errors for this API.

comments powered by Disqus