Configuring Agents

CodeLogic Change Requests automatically find scans of the changes from a pull request in one of two ways. The CodeLogic server will locate the scan data based on the git hash matching the hash provided by the webhook, or it will locate the scanned artifact data in a specially named Scan Space correlating to the pull request.

Note

Using named Scan Spaces is recommended when setting up Change Requests as it does not clutter the Default Scan Space with scans from pull requests. Once a pull request is closed, the correlating pull request Scan Space is automatically removed by the CodeLogic server, minimizing disk usage.

Using Named Scan Spaces

The CodeLogic server will look for scanned artifact data in a Scan Space with a pattern matching REPOSITORY_URL|BRANCH_NAME. To configure an agent to scan into a named Scan Space, please refer to the agent configuration documentation.

As an example, if your pull request originates from the following repository https://github.com/CodeLogicIncEngineering/blog_references in a branch named feature/CAPE-1983 you would pass the following Scan Space to the agent when scanning: https://github.com/CodeLogicIncEngineering/blog_references|feature/CAPE-1983.

Git Hash Lookup

Agents automatically locate and collect git information when scanning. The CodeLogic server uses this information to match the scanned artifacts with the appropriate pull request by utilizing the git hash. If git information is not available to the agents, you can manually specify a uniquely named Scan Space for the agent to store the artifact scans, which Change Requests can utilize for locating the appropriate data.