GitHub Enterprise Setup in Provar Grid

Introduction

Provar Grid supports the use of many different suppliers of Version Control Systems, including Github, Bitbucket, and Azure DevOps. For public repositories, these can be used out of the box without any need for further configuration.

However, some settings must be configured to use GitHub Enterprise Server or Cloud account types. This document describes the steps that need to be taken.

Firewall settings

For Provar Grid to execute jobs, Provar’s services must extract the Provar Project from the repository at runtime. Where the repository is stored in Github Enterprise and if the server is used for the Github Enterprise service restricts the IPs with access. Then, a defined range of IP addresses will need to be whitelisted so they can access the GitHub Enterprise Cloud or Server repositories.

Note: This is not necessary for Public Github repositories.

The following are CIDR blocks of IP addresses that must be whitelisted.

• 137.135.87.44/32
• 20.84.36.156/31
• 207.254.54.36/32
• 199.7.167.10/32
• 207.7.135.68/26

Note: These are CIDR blocks and not exact IP addresses. To obtain the verbose list of IP addresses included, you can expand the CIDR block here.

SSL Certification

It is considered best practice to use an SSL Certificate on the GitHub Enterprise Server. However, Provar recognizes that this may not always be the case.

Therefore, Provar has included an optional toggle in the ‘VCS Connection Assistant;’ make sure it is enabled if an SSL certificate is present and disabled if not.

Remote Server Settings

To import Repository and Branch references into your Provar Manager application, your Salesforce org must call out to the GitHub Enterprise Cloud or Server repository. To do this, Salesforce requires that the target site be added as a record in the ‘Remote Site Settings.’

To do this, follow the below steps:

1. From your Salesforce org, launch ‘Setup.’
2. Quick search to ‘Remote Site Settings.’
3. Click ‘New Remote Site.’
4. Enter a descriptive term for the ‘Remote Site Name.’
5. Enter the URL for the remote site.
6. Select the Disable Protocol Security checkbox to allow access to the remote site regardless of whether the user’s connection is over HTTP or HTTPS. When selected, Salesforce can pass data from an HTTPS session to an HTTP session and vice versa. Only select this checkbox if you understand the security implications.
7. Optionally, enter a description of the site.
8. Click Save to finish.

For further information, please refer to this Salesforce article.