Buildkite Pipelines
Buildkite Pipelines is a hosted, distributed continuous integration service used to build and test software projects.
This how-to will provide a basic understanding of how add the Relyance Source Code inspector (SCI) into a typical build job.
Prerequisites:
- A source code repository needs to be available in Buildkite.
- Ensure Docker is available on the Buildkite agent.
- The
relyance.yamlfile needs to be in the source code root directory. - Grab the command line code from Step 2 of the Relyance Source Code Integration settings from your Relyance instance. See more info about the SCI commands here.

Steps:
- Log in to Buildkite.
- Create a new pipeline / or select the pipeline you wish to add to. i. If creating a new pipeline, select the repository you would like to connect. ii. If adding to an existing pipeline, click Add> Run script or command.
- Paste the Step 2 command into the the Commands to run box in the Steps section.
- Click Create pipeline/ Save Steps.
- Once ready, go to the pipeline and click the New Build button.
- If there are no errors, you should start to see SCI results in your Relyance tenant.

Appendix:
Source Code Integration Step 2 info:
Example Step 2 Command
| 1 | docker pull gcr.io/relyance-ext/compliance_inspector:release && \ |
|---|---|
| 2 | docker run --rm -v pwd:/repo --env 'API_KEY= example :abcdefg0123456789abcdefg0123456789abcdefg' gcr.io/relyance-ext/compliance_inspector:release |
- This command pulls the latest version of the Relyance Source Code Inspector.
- This command initiates the Relyance Source Code Inspector within a local Docker container, establishing a shared folder and providing the necessary tenant API credentials.