Defining Office 365 Git Repository

Setting up your instances #

In order to be able to scan your instances, you need to point Quality Clouds to them.

→ To create an instance in Quality Clouds #

1. Login to the Quality Clouds portal at https://portal.qualityclouds.com/.
2. Go to Account > Instances section.
3. Select the O365 tab (if you use several SaaS with Quality Clouds), and click the + (add instance) button.
4. Select Git repository, and fill in the following information:
   • Description – Short and meaningful description of the instance. For example: MyCompany UAT
   • Environment – Environment type of the instance. This is used to add descriptive context to your instance.
   • Git Flavor – Git Repository type, to select among: GitHub/GitLab, Bitbucket, Azure DevOps/Visual Studio.
   • Git Repository URL – URL of the Git Repository.
   • Feature Branch – Enable if you want to scan a feature branch. When selected, the scan will report only differences between the specified feature branch and the reference branch. As feature branches names can vary, branch name will be requested before scanning.
   • Branch – Name of the reference branch to scan. 
   • User ID – Username to access the Git Repository.
   • Password – Password credential for the Git User.
   • Go-live Date – Date on which the instance was first started, serves as a baseline for Org changes.
   • First-scan Date – Date on which the first scan was first launched.
   • Tags – Use tags to add specific information for better instance recognition.
     
5. Click Save. 

→ Configure the Quality Gates #

1. When setting or editing an instance, click on the ‘Quality Gates’ tab.
2. Enable the Quality Gates toggle.
3. Add the Activation Date.
4. Configure the Blocking rules table and smart tagging.
5. Click ‘Save‘.

Click here to learn how Quality Gates work.

→ Configure the Peer Review #

1. When setting or editing an instance, click on the ‘Peer Review’ tab.
2. Enable the Peer Review toggle.
3. Select when to get notified when Peer Reviews are pending: None, Daily, Weekly or Monthly.
4. In the Peer Review Workflow section select ‘Write Off assignation’:
   • Manual Assign
   • Auto Assign
   • Developer Assign
5. Select the Default assignee email on the dropdown menu. Enable it if you want the default assignee to be notified when a write-off is assigned.
6. Enable or disable the Source Code toggle.
7. Click ‘Save‘.

• Manual Assign will hide the Default Assignee drop-down menu. 
• Auto Assign will show the Default Assignee and there won’t be any other option than to select one person from the list.