![]() ![]() Step 2: Configure the GitLab Pipelines configuration file and include code analysis Scroll down to Merge checks and make sure that both are checked: Go to Settings > General and expand the Merge Requests section. Step 1: Mandate successful merge checks Īs a GitLab administrator, you can edit your project properties to enforce branch protection rules. Name it MR_TOKEN for use in the bash script used to run preZero, and make sure to assign it the api and read_api scopes. GitLab API access Ĭonfigure a personal access token to authenticate Qwiet with the GitLab API. Please note that the presence of any set environment variables will override those in a configuration file. You can create your CI token in the Qwiet Dashboard. However, when running in a production environment, we recommend using a CI token as the access token. Name this variable SHIFTLEFT_ACCESS_TOKEN, and set it to the value found in the Dashboard under Access Token. Set the environment variable Ĭreate a custom environment variable so that GitLab can communicate and use Qwiet. To facilitate communication between Qwiet and GitLab, please create the required environment variables and API access token as described in the following two sections. We assume that you're working with a GitLab repo that utilizes GitLab's built-in CI pipelines and Linux-based runners, though you could use GitLab's as an alternative. Integrating preZero into your GitLab Merge Request workflow is done using the pipelines for merge requests that GitLab includes in its premium version. This article shows you how to integrate Qwiet preZero into your GitLab Merge Request Workflow for automated code analysis whenever you create a new PR. Integrate preZero into the GitLab Merge Request Workflow
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |