zulip/templates/zerver/integrations/openshift.md

This integration sends a notification every time a deployment is made
in an OpenShift instance.

1.  {!create-stream.md!}

1.  {!download-python-bindings.md!}

1.  Then, create a new commit including all the changes made to the
    repository, and push it to your app.

1.  After that, connect to the application through SSH. If you don’t know
    how to do this, log in to your OpenShift Online account, go to your
    application’s dashboard, and click **Want to log in to your
    application?**.  There you’ll find the app’s SSH user, address, and
    further information on SSH, in case you need it.

    ![Connecting to application](/static/images/integrations/openshift/002.png)

1.  {!change-zulip-config-file-indented.md!}

1.  You can also specify which pushes will result in notifications and to
    what stream the notifications will be sent by modifying the
    `deployment_notice_destination` function in
    `zulip_openshift_config.py`. By default, deployments triggered by
    commits pushed to the `main`, `master`, and `test-post-receive` branches will
    result in a notification to stream `deployments`.

1.  Save the file, and symlink
    `$OPENSHIFT_PYTHON_DIR/virtenv/share/zulip/integrations/openshift/post-receive`
    into the `~/app-root/repo/.openshift/action_hooks` directory.

1.  Whenever you make a push to the `main` branch of your application’s
    repository (or whichever branch you configured above), or if you force
    a deployment, the Zulip OpenShift plugin will send an automated
    notification.

{!congrats.md!}

![OpenShift integration message](/static/images/integrations/openshift/001.png)

### Testing

You can test the plugin without changing your `main` branch by pushing to the `test-post-receive` branch.