CI/CD and container images
How Facets works with the CI pipeline you already have, how a container image reaches an environment, and how to run a job after a release.
Your CI keeps building and testing your code, and Facets deploys the container images it produces.
Using your CI pipeline, and running jobs after a release
Any CI that can run a command works with Facets.
- Your CIBuild and testJenkins, CodeBuild, GitHub Actions or any other CI builds the imagepushes the image to a
- RegistryContainer registryECR, Google Artifact Registry, ACR, Docker Hub, JFrog, Nexus or another registryand registers it with Facets as an
- deployed by the next
Today, the only release hook runs before a release. For a job after one, your CI can wait for the release to finish, or subscribe a webhook to deployment notifications.
Secrets and variables
How a service gets its database's address and credentials, where Facets keeps secrets, using your own AWS Secrets Manager, and whether release logs show them.
Operations, debugging and cloud cost
How to find what changed when something breaks, how drift and upgrades are handled, and the restart, scaling, monitoring and cost tools Facets includes.