# Build Integrations ## Currently Supported Integrations * Azure DevOps * Jenkins Pipeline * Bitbucket Pipeline * Circle CI * GitHub Actions * Gitlab Pipeline ## Build Integration Steps Threatrix [Threat Agent](/threat-agent/threat-agent-1.md) runs scans from within your build environment, allowing for automated and continuous open source security and license compliance data to be sent to your team. As a build step, scans run during a build and are typically kicked off during a pull request. Integrated scans enable your development to spot security problems, in your open source, before merging their changes into your main branch. [Scan summary reports](/threat-agent/scan-summary-reports.md) can be generated to annotate your pull request making it fast and easy for developers to find and fix vulnerabilities and license violations. **Just a few simple steps are required to get you up and running.** 1. Collect the information required to configure your build environment. 2. Configure your build server with the environment variables. 3. Add a build step to download Threat Agent and execute a scan. ### Environment Variables Whlle these values can be passed directly to the agent on the command line, it's often more security and helpful to implement them as environment variables within your build server. * THREATRIX\_OID \[REQUIRED]: The organization ID - Found in admin and user profile. * THREATRIX\_EID \[REQUIRED]: The entity ID for which scan results will be associated. This must be an entity for the user associated with the API\_TOKEN to have rights. * THREATRIX\_API\_KEY \[REQUIRED] - The access key used for the scan. Found in the admin or user profile ### Threat Agent Scan Options Our Threat Agent requires minimal configuration as it can detect it's environment and self configure based on that context. However, several [command line options](/threat-agent/install-config.md#scan-flags) and scan are available. ### Build Server Configuration Please see the respective build server documentation. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.threatrix.io/integrations/build-integrations.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.