Create DevOps Gate Process

Overview

This document describe the procedure to setup a devops gate process

Create a new DevOps Gate Process

1. Navigate to the DevOps Gate page
2. Press the Add DevOps Gate Process button

Configure System Security with DevOps Gate

3. Open another browser tab, go to the Systems page
4. Press the edit button of systems that are in the DevOps Process

5. Select preferable Webhook Security options
   1. Restrict Webhooks to specific IP Addresses
   2. Allow Anonymous web hook notifications DevOps Gate or User SyncNow username account for authenticating webhook requests in to the system.
      
6. Save the system configuration

Using Anonymous web hook notifications is not recommended and dangerous.We highly recommend setting the origin IP Address for the work systems from which webhooks are issued to SyncNow

Configuring the DevOps Gate Process

7. Set a name for the process
8. Select systems from which to receive a WebHook and a target system where update entities
9. Add unique system prefixes. By these prefixes the service will recognize from which system is an entity and which entity should be updated
10. Select allowed target sub projects. Only an entity from allowed projects will be created or updated, and only to entities from the allowed sub projects will be added a comment;
11. Select Create | Update | Upload Attachments action
12. Press the Save button

A new DevOps Gate Process has been created

Set DevOps Gate Process Mapping

13. Press the Mapping Entities button
14. Add entities pairs. On each API call will be created (or updated previously created) as many entities as many entity types will be added to the mapping (on image below it is only one entity). System connectors without entities such as jenkins or generic system (for API calls) allow mapping only SyncNow Virtual Entity to another target entity. Generic System and Jenkins can be only the source

Field Mapping

13. Press the Mapping Fields button

16. Add as many fields as needed. For Generic System only SyncNow Virtual Field is available, but you can define fields with any names, every name defines a parameters received from the source system side and mapped to target field , generic system and jenkins can be only be the source of the process.
17. Press the Save button
18. Press the Edit Field button to open the dialog with advanced field definitions

19. Set C# or Constant data transformation for mapped fields if needed to any value received from systems