Integrating with Travis CI

Connect Your Application

Visit Connected Applications on the sidebar. Click on the Connect button for Travis CI.

Once the connect button is clicked in Valven Atlas Connected Applications, a pop-up with guidance to complete the integration and a UUID will be presented for the webhook configurations in Travis CI.

Once you click the "Save" button, we will assume the configuration on the Travis CI side is completed and show the connected Travis CI section. 

The integration between Valven Atlas and Travis CI mostly requires configurations on the Travis CI side with the generated UUID. The webhook configuration should be completed to establish communication between Travis CI and Valven Atlas.

Important Notes!

If the release is to be installed in production, you need to send a webhook to Atlas at the end of the workflow.
The webhook should not be sent to Atlas for releases that will not be installed in production.

Webhook Configuration

Add the following notification configurations to the end of the ".travis.yml" file in your repository.
If it conflicts with your existing notification settings, you can configure it in a way that only pipelines that have completed the deploy stage can send webhooks.

notifications:

  webhooks:

    urls:

      - http:/webhook-atlas.valven.com/api/deployment/<UUID>

    on_success: always

    on_failure: never

    on_start:   never

    on_cancel:  never

    on_error:   never

Related Configurations:

UUID: Obtained after clicking on the Connect in Valven Atlas Connected Applications for Travis CI.