OpenShift | Zulip integrations

Logos are trademarks of their respective owners. None of the integrations on this page are created by, affiliated with, or supported by the companies represented by the logos.

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

Create the channel you'd like to use for OpenShift notifications.
Download and install our Python bindings and example scripts on the server where the OpenShift bot will live.
Then, create a new commit including all the changes made to the repository, and push it to your app.
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.
Open /usr/local/share/zulip/integrations/openshift/zulip_openshift_config.py with your favorite editor, and change the following lines to specify the email address and API key for your OpenShift bot:
```
ZULIP_USER = "openshift-bot@example.com"
ZULIP_API_KEY = "0123456789abcdef0123456789abcdef"
ZULIP_SITE = "https://veraison.zulipchat.com/api"
```
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.
Save the file, and symlink $OPENSHIFT_PYTHON_DIR/virtenv/share/zulip/integrations/openshift/post-receive into the ~/app-root/repo/.openshift/action_hooks directory.
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.

You're done! Your OpenShift notifications may look like this:

OpenShift integration message

Testing

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

Logos are trademarks of their respective owners. None of the integrations on this page are created by, affiliated with, or supported by the companies represented by the logos.

And hundreds more through Zapier and IFTTT.

Filter by category

All

Interactive bots

Communication

Continuous integration

Customer support

Deployment

Entertainment

Financial

Human resources

Marketing

Integration frameworks

Miscellaneous

Monitoring

Productivity

Project management

Version control

Custom integrations

Incoming webhooks

Interactive bots

REST API

Categories

All

Interactive bots

Communication

Continuous integration

Customer support

Deployment

Entertainment

Financial

Human resources

Marketing

Integration frameworks

Miscellaneous

Monitoring

Productivity

Project management

Version control

Custom integrations

Incoming webhooks

Interactive bots

REST API

Airbrake

Monitoring

Airbyte

Monitoring

Prometheus Alertmanager

Monitoring

Ansible Tower

Deployment

AppFollow

Customer support

AppVeyor

Continuous integration

Asana

Project management

Assembla

(Hubot script)

Version control

AzureDevOps

Version control

Basecamp

Project management

Beanstalk

Version control

Beeminder

Miscellaneous

BigBlueButton

Communication

Bitbucket

(Enterprise)

Version control

Bitbucket

Version control

Bitbucket Server

Version control

Bonusly

(Hubot script)

Human resources