Skip to content

Continuous Deployment

Rio enables continuous deployment with GitHub by default. This allows developers to streamline their focus on their git repository and worry less about their deploys.

The most versatile use case is in this example.

Basic Example

Deploy a workload with Rio from a public GitHub repository that you have push access to:

rio run -n cd-demo -p 8080

Make a commit to the master branch of the repo. You should notice that within 15 seconds, Rio rebuilds your workload (rio build-history) and updates it to match the committed changes.

Advanced Usage

Pull Request Builds

This feature uses a webhook to create a deployment when submitting a Pull Request to your tracked branch (master by default). A new workload version will be staged in Rio, associated to the same app that was initially created. You can view the endpoint results directly from the PR by clicking "View deployment" in GitHub. If the pull request is merged, it will then update the app endpoint in Rio to point to this new version.

It only takes 2 steps:

  1. Configure Webhook for your repository. For this example, you only need to set the webhook up.
  2. Run
rio run -p 8080 -n example-cd --build-webhook-secret=githubtoken --build-pr --template

NOTE: if your repository is private, you will also need to create a credentials secret and use the correct additional flags when running your workload.

Automatic Versioning

Notice the --template flag specified in the Pull Request Builds scenario. With this flag set, Rio will automatically configure versions for this workload when new commits are pushed to the GitHub repo. As soon as the workload is ready, it will promote that version to have 100% of the app endpoint weight. The only case where it won't automatically promote is when using the --build-pr flag as well and the build is from the PR branch.

If the --template flag is not set, then every subsequent build will overwrite the current version, including builds from the PR branch with --build-pr flag set.

Private Github Repo

You can do this with Git Basic Auth or SSH Auth: - Git Basic Auth: 1. Configure git basic auth credential secrets:

    $ rio secret create --git-basic-auth
    Select namespace[default]: $(put the same namespace with your workload)
    git url[]: $(for example:
    username[]: $(your GH username)
    password[******]: $(your GH password)

2. Rio will automatically use this secret now when doing standard git checkout, so no additional flags need to be passed. For example:

   rio run -p 8080
  • SSH Auth:

    1. Configure git sshkey auth credential secrets. This should use a key that does not have a password associated to it:

      bash $ rio secret create --git-sshkey-auth Select namespace[default]: $(put the same namespace with your workload) git url[]: $(put your github url. Leave out http/https. Example: ssh_key_path[]: $(type the path to your ssh private key)

    2. Tell rio to do ssh checkout from git. For example:

    bash rio run --build-clone-secret gitcredential-ssh -p 8080 [email protected]:example/example.git

Private Docker Registry

Configure the Docker credential secret.

$ rio secret create --docker
Select namespace[default]: $(put the same namespace with your workload)
Registry URL[]: $(found with "docker info | grep Registry")
username[]: $(your docker username)
password[******]: $(your docker password)

Push your image to docker registry:

rio run --image-pull-secrets dockerconfig --build-docker-push-secret dockerconfig -p 8080 --build-registry --build-image-name $username/repo

Useful Options

There are many options available for use when running workloads in Rio. These are just a few that are useful for CD:

Option Type Description
--build-branch string Build repository branch (default: "master")
--build-dockerfile string Set Dockerfile name, defaults to Dockerfile
--build-context string Set build context, defaults to .
--build-webhook-secret string Set GitHub webhook secret name
--build-clone-secret string Set git clone secret name
--build-image-name string Specify custom image name to push
--build-pr boolean Enable pull request builds
--build-timeout string Timeout for build, default to 10m (ms
--image-pull-secrets string Specify image pull secrets
--template boolean If true new version is created per git commit. If false update in-place