Trigger Scan
Once you have configured the pipeline script, you can trigger a scan in the following ways:
Trigger Scan (Automatically)
The IaC scan is automatically triggered on every push request and merge request. Once the script is configured, the script is automatically executed, and the scan is triggered with every push request and merge request. With every such action, the committed or merged files that were added to the branch are scanned.
Trigger Scan (Manually)
You could manually trigger a scan for the entire repository.
- In GitLab, navigate to your project.
- Click CI/CD > Pipelines.
- Click Run pipeline.
The Run pipeline screen is displayed.
-
In the Run for branch name or tag field, select the branch or tag for which you want to trigger the scan.
-
Click Run pipeline.
The scan is initiated on all the files in the selected branch of your repository. To scan all the files in the repository, select the trunk branch.
Trigger Scan (Scheduled)
You could schedule the IaC scans to be executed at a scheduled time at specific intervals.
- In GitLab, navigate to your project.
- Click CI/CD > Schedules.
- Click New schedule.
The Schedule a new pipeline screen is displayed.
-
Enter the description for the new schedule.
-
Select the required option from Interval Pattern and add the appropriate value in the field.
The schedule timing is configured with cron notation.
-
Select UTC from the Cron Timezone drop-down.
-
Select the branch on which you want to trigger the scan from the Target Branch drop-down.
-
Click Save pipeline schedule.
You can see a list of scheduled pipelines on the Schedules index page. The server automatically calculates the next run GitLab is installed on.
Next step: