From ebdd7a0dc74c6b7baeff68d5ba98aeb4ec052f43 Mon Sep 17 00:00:00 2001 From: David Karlsson <35727626+dvdksn@users.noreply.github.com> Date: Tue, 26 Sep 2023 10:29:07 +0200 Subject: [PATCH] scout: cross-reference to env monitoring from ci Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com> --- content/scout/integrations/ci/_index.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/content/scout/integrations/ci/_index.md b/content/scout/integrations/ci/_index.md index f20dbac3e7..11cb253d39 100644 --- a/content/scout/integrations/ci/_index.md +++ b/content/scout/integrations/ci/_index.md @@ -18,4 +18,8 @@ Available integrations: - [GitLab](gitlab.md) - [Microsoft Azure DevOps Pipelines](azure.md) - [Circle CI](circle-ci.md) -- [Jenkins](jenkins.md) \ No newline at end of file +- [Jenkins](jenkins.md) + +You can also add runtime integration as part of your CI/CD pipeline, which lets +you assign an image to an environment, such as `production` or `staging`, when +you deploy it. For more information, see [Environment monitoring](../environment/_index.md).