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 action, such as pull requests and push requests. Once the script is configured, the script is automatically executed, and the scan is triggered with every push request and pull request. With every such action, the new files that were added to the branch that performed the pull operation are scanned.
Trigger Scan (Manually)
You could manually trigger a scan for the entire repository.
- On the Bitbucket console, go to Repository > Pipeline > Run Pipeline.
The Run Pipeline dialog box is displayed.
-
Select the branch on which you want to trigger the scan from Branch drop-down.
-
Select custom: qualys from the Pipeline drop-down.
-
Click Run.
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 on an hourly, daily, or weekly basis.
- On the Bitbucket console, go to Repository > Pipeline > Schedule.
The Create a Schedule dialog box is displayed.
-
Select the branch on which you want to trigger the scan from the Branch drop-down.
-
Select custom: qualys from the Pipeline drop-down.
-
Select the frequency at which you want the IaC scan to be automatically triggered. You could choose from Hourly, Daily, or Weekly options. You could also configure the time at which the scan should be triggered.
-
Click Create.
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.
For more information on Bitbucket pipeline triggers, refer to https://support.atlassian.com/bitbucket-cloud/docs/pipeline-triggers/