When integrating Secure Source Manager with other CI/CD solutions, the recommended
approach depends on your network environment. If your CI/CD tools
exist within public networks, you can use public endpoints to connect them.

In a default public network configuration, services connect over the
public internet. This configuration requires fewer steps to set up
than private network integrations, but exposes the services to the internet.

Secure Source Manager supports a built-in integration with Cloud Build
using build configuration and trigger files. For other CI/CD solutions,
you can use webhooks.
![Architecture showing Secure Source Manager connected to external tools through public endpoints](https://docs.cloud.google.com/static/secure-source-manager/docs/images/public_network_integration.svg) Public network integration architecture

For more information about setting up Secure Source Manager on a public network, see:

- [Connect to Cloud Build](https://docs.cloud.google.com/secure-source-manager/docs/connect-cloud-build)
- [Connect to Jenkins](https://docs.cloud.google.com/secure-source-manager/docs/connect-jenkins)
- [Set up webhooks](https://docs.cloud.google.com/secure-source-manager/docs/set-up-webhooks)

## What's next

- [Connect to Cloud Build](https://docs.cloud.google.com/secure-source-manager/docs/connect-cloud-build).