diff --git a/docs/2-attack-of-the-pipelines/3b-tekton.md b/docs/2-attack-of-the-pipelines/3b-tekton.md index 0c1c8031..cfb62085 100644 --- a/docs/2-attack-of-the-pipelines/3b-tekton.md +++ b/docs/2-attack-of-the-pipelines/3b-tekton.md @@ -144,6 +144,7 @@ In this snippet of the pipeline used in this exercise, we define: ```bash#test echo https://$(oc -n ${TEAM_NAME}-ci-cd get route webhook --template='{{ .spec.host }}') ``` +_Note: If you are seeing PVCs are still in Progressing status on Argo CD, it is because the OpenShift cluster is waiting for the first consumer aka the first pipeline run to create the Persistent Volumes. The sync status will be green after the first run ☘️_ 8. Once you have the URL, over on GitLab go to `pet-battle-api > Settings > Integrations` to add the webhook: diff --git a/docs/2-attack-of-the-pipelines/images/gitlab-webhook-trigger-fe.png b/docs/2-attack-of-the-pipelines/images/gitlab-webhook-trigger-fe.png index b8500a5a..5b37f779 100644 Binary files a/docs/2-attack-of-the-pipelines/images/gitlab-webhook-trigger-fe.png and b/docs/2-attack-of-the-pipelines/images/gitlab-webhook-trigger-fe.png differ diff --git a/docs/2-attack-of-the-pipelines/images/gitlab-webhook-trigger.png b/docs/2-attack-of-the-pipelines/images/gitlab-webhook-trigger.png index dff5d7a1..17a1d851 100644 Binary files a/docs/2-attack-of-the-pipelines/images/gitlab-webhook-trigger.png and b/docs/2-attack-of-the-pipelines/images/gitlab-webhook-trigger.png differ diff --git a/docs/3-revenge-of-the-automated-testing/8a-jenkins.md b/docs/3-revenge-of-the-automated-testing/8a-jenkins.md index e3552f0a..dbf3b394 100644 --- a/docs/3-revenge-of-the-automated-testing/8a-jenkins.md +++ b/docs/3-revenge-of-the-automated-testing/8a-jenkins.md @@ -53,7 +53,7 @@ 🪄 Observe the **pet-battle** pipeline running with the **image-sign** stage. ![cosign-jenkins-pipeline](images/cosign-jenkins-pipeline.png) - After the pipeline succesfully finish, go to OpenShift UI > Builds > ImageStreams inside `-test` namespace and select `pet-battle`. You'll see a tag ending with `.sig` which shows you that this is image signed. + After the pipeline succesfully finish, in the `Administrator` view, go to OpenShift UI > Builds > ImageStreams inside `-test` namespace and select `pet-battle`. You'll see a tag ending with `.sig` which shows you that this is image signed. ![cosign-image-signing-pet-battle](images/cosign-image-signing-pet-battle.png) diff --git a/docs/3-revenge-of-the-automated-testing/8b-tekton.md b/docs/3-revenge-of-the-automated-testing/8b-tekton.md index fc94ac3d..12be0a4c 100644 --- a/docs/3-revenge-of-the-automated-testing/8b-tekton.md +++ b/docs/3-revenge-of-the-automated-testing/8b-tekton.md @@ -88,7 +88,7 @@ 🪄 Observe the **pet-battle-api** pipeline running with the **image-sign** task. - After the task successfully finish, go to OpenShift UI > Builds > ImageStreams and select `pet-battle-api`. You'll see a tag ending with `.sig` which shows you that this is image signed. + After the task successfully finish, in the `Administrator` view, go to OpenShift UI > Builds > ImageStreams and select `pet-battle-api`. You'll see a tag ending with `.sig` which shows you that this is image signed. ![cosign-image-signing](images/cosign-image-signing.png)