Source control integrations let HoundDog.ai import your repositories and roll out CI scan configurations across them in bulk — as direct commits or as pull requests requiring approval. For organizations with many repositories, this turns months of CI plumbing into minutes.
Supported platforms:
- GitHub Cloud — via the HoundDog.ai GitHub App.
- GitHub Enterprise — GitHub Enterprise Cloud and Server.
- Bitbucket Data Center — via an access token.
Scan Settings
Section titled “Scan Settings”Scan settings are chosen per CI rollout in the Set up CI dialog:
- Pull request scans — run a scan when pull or merge requests are created or updated.
- Periodic scans — run scheduled scans daily or weekly.
- Build blocking — terminate the CI job with exit code 1 when dataflows at or above a chosen severity threshold are found. This also blocks pull requests, since the check fails.
- CI runner — the type and name of the CI runner to use.
- Ignore file patterns — paths to exclude from scans, such as test folders.
Primary Branch and Ignore File Patterns can additionally be overridden per repository on the repository detail page.
Delivering CI Configuration
Section titled “Delivering CI Configuration”After selecting repositories, preview the generated CI configuration files, then deliver them either as a Commit Directly or as a Create Pull Request requiring approval from a repository administrator.
Connections can also enable automatic repository import, which runs weekly to discover and import new repositories into HoundDog.ai.