Which of the following is NOT a recommended approach for managing scanner jobs?

When managing scanner jobs within a CI/CD pipeline, it is important to maintain an efficient and effective workflow. Blocking the pipeline with scanner jobs can lead to significant delays in the overall development process. This is especially true if the scan is lengthy, as it can cause other jobs and stages to be held up, preventing timely feedback and slowing down the release of code.

In contrast, utilizing options such as allow_failure can help improve workflow by allowing the pipeline to continue executing other jobs even if the scanner job fails. This approach prevents bottlenecks and allows teams to focus on fixing issues without interrupting the deployment cycle. Building from official distributions and keeping image sizes small are also best practices, ensuring that the build process remains efficient and manageable.

By avoiding the practice of allowing scanner jobs to block the pipeline, teams can enhance their continuous integration and delivery processes, facilitating quicker iterations and a more agile response to project demands.