HailBytes + Jenkins

What you get

• Declarative-pipeline snippet. Drop a stage into an existing Jenkinsfile — no plugin install, no controller restart, nothing to get through change management.
• Credentials binding. The API key comes from the Jenkins credentials store, not from pipeline source.
• SARIF archival. Results archived as build artifacts for gating or retention as release evidence.
• Jenkins LTS 2.426+. Tested on Linux and Windows agents.

Deliberately documentation rather than a plugin: for teams running Jenkins on-premises — often the ones with the strictest change control — a reviewable pipeline stage is easier to get approved than a new controller plugin.

It calls the same shared hailbytes-scan.sh as our GitHub, GitLab, CircleCI, and Azure Pipelines integrations, so behaviour matches across all five.

You operate your own Jenkins controller and agents. No hosted component on our side.