Skip to main content
System StatusContact Support
VersionOne Community

GitHub Setup for Continuum

Overview

GitHub has the ability to send a Json payload to a webservice endpoint upon a developer commit push. In this document we will configure a temporary webhook to test network connectivity to Continuum.

The following steps work for GitHub.com as well as GiHub Enterprise.

Networking Requirements

GitHub will need outbound access to push events to Continuum on the default port of 8080. Contnuum will need inbound access on the same port.

Setup Temporary Test Webhook

  1. Login to your GitHub application and select a repository to setup the webhook on.

  2. Click the Settings tab towards the top of the page (looks like a gear).

  3. Click Webhooks & services on the left.

  4. Click on the Add Webhook button. You may be asked to enter your password.

  5. In Payload URL you will want to enter the Continuum address as in the example that follows: http://continuum.mycompany.com:8080/api/submit_change

  6. Make sure Active is checked and Just the push event is selected. Click the Add webhook button.

Test the Webhook Push

  1. When you clicked the Add webhook button you should have returned to the Webhooks page.

  2. Click on the new webhook to see how GitHub's test POST did.

  3. Click on the request made under Recent Deliveries at the bottom of the screen.

  4. Next to Request you should see Response 400.

  5. Scroll down you will see the body that was returned. The following response is what we want:

{
    "ErrorCode": "AuthenticationFailure",
    "ErrorDetail": "",
    "ErrorMessage": "Authentication Failure",
    "Method": "",
    "Response": ""
}

We attempted to POST the changes unauthenticated to the Continuum REST API. Since we are simply testing connectivity for now this error is the one we are expecting.

Any other errors beside the Authentication Failure error need to be resolved. These typically will be server address, port or networking issues that will need to be resolved (e.g. if a TIMEOUT occurs). If you need to make changes to the webhook URL, repeat the process of Update webhook and then viewing the Recent Deliveries. You can also click on the Redeliver button to test network connectivity issues.

Common problems to look for:

  • Wrong Continuum server address and port

  • Network access from GitHub server to Continuum server

  • Local firewall on Continuum server needs to allow port 8080

  • GitHub webhook not enabled for repository

  • Commit was not pushed to GitHub

If you continue to have problems with getting the changes posted from GitHub to Continuum, contact support@versionone.com.

Delete the Temporary Webhook

We return to create a more permanent webhook later. For now return to the Webhooks page and delete the temporary webhook.

Next

Return to Connecting to Tools

  • Was this article helpful?