GitHub has the capability to post json formatted data on commit pushes. These are called webhooks. This section describes how to setup these webhooks.
First in the VersionOne Continuum application you must get an authentication token for the webhook to use. The first step of this tutorial showed how to get to the API token. You will need this now.
Next login to the GitHub user interface and find the webhook setting for the repository you wish to connect to Continuum.
GitHub doc: https://developer.github.com/webhooks/creating/
For GitHub make sure Content type is
Just the push event is selected.
In the URL text box, you will want to add a url as follows:
- "continuumaddress" will be the address of the Continuum server
- "continuumproject" will be the project created in the first step of this tutorial
- "apitoken" will be the user’s API token found above
Test the Webhook Push
Now submit a change to your GitHub repository. This simply can be a change to a file, commit and push. Now in the Continuum app in the menu across the top select
projects. Click on your new project. Whereas the Manage Projects page is used for setting up and configuring projects in Continuum, this page is more of an informational page.
Manifest tab on the left. Expand the Changes block, you should see one change submitted which will match the one pushed.
When GitHub pushed the change to the Continuum REST API, the Json payload was converted into a normalized Change record in Continuum. This change can now be tracked throughout its lifecycle.
Click on the project name, then on the Version tab on the left. Expand the Changes section. If everything went fine, you should see the change that came in listed here. Clicking on that row will show additional details of the change including who made the commit, the log and a list of the files involved.
If everything went ok, then skip to the next section. Otherwise let's troubleshoot.
Most problems with webhook submission will be related to wrong project names, a blocked port through a firewall or a wrong token string.
Click here to continue on with the tutorial once the Stash changes are viewable in Continuum.