When integrating Secure Source Manager with other CI/CD solutions, the recommended
approach often depends on your network environment. If your CI/CD solution
combines public and private networks, and some deployment tooling
isn't a Google Cloud service, then you can use a mixed-network integration.

Architecture for a mixed-network integration generally involves connecting
Secure Source Manager to third-party CI/CD tools that are on-premises or in an
external network.
![Mixed network architecture diagram showing Secure Source Manager
communicating via Private Service Connect and public endpoints](https://docs.cloud.google.com/static/secure-source-manager/docs/images/mixed_network_integration.svg) Figure 1. Mixed network integration architecture.

For step-by-step instructions on setting up this type of integration with
third-party tools, see:

- [Connect to Jenkins](https://docs.cloud.google.com/secure-source-manager/docs/connect-jenkins.md.txt)
- [Create a Private Service Connect instance](https://docs.cloud.google.com/secure-source-manager/docs/create-private-service-connect-instance.md.txt)

## What's next

- [Learn about webhooks](https://docs.cloud.google.com/secure-source-manager/docs/webhooks-overview.md.txt).