fortify-cicd-integration

To integrate Fortify scanning into GitHub Actions or GitLab CI, this Skill analyzes your repository to detect the active CI/CD platform and generates a tailored, platform-aware workflow outline with pointers to official documentation.

Yes, you can use Fortify with both FoD and SSC deployments in Jenkins. The Skill identifies your specific Fortify deployment type and recommends appropriate authentication methods and URL handling to avoid exposing secrets in code.

The best way to automate Fortify CI/CD integration is to use a reference-driven approach that infers your build toolchain from manifests and generates workflow steps aligned with official platform-specific guidance files.

Yes, specifying your deployment region is required. The Skill detects missing inputs like FoD or SSC deployment type and region, prompting you to provide these necessary details before generating the final workflow.

Fortify workflow generation prompts for missing details to ensure the generated pipeline configuration is fully functional. It validates required inputs like deployment type and region before creating the output to prevent integration errors.

Fortify environment inference works by analyzing your build manifests to detect the programming language and toolchains. It then produces a tailored workflow outline that aligns scanning steps with your specific build environment.