Final content for first day of 20231130/20231207

Author: nicholasdille

160_gitlab_ci.yml

@@ -89,6 +89,7 @@ nav:
   - GitLab: 000_rollout/exercise_gitlab.md
   - IDE: 000_rollout/exercise_ide.md
   - Project: 000_rollout/exercise_project.md
+  - You are ready: you_are_ready.md
 - Basics:
   - Jobs and Stages: 010_jobs_and_stages/exercise.md
   - Variables: 020_variables/exercise.md
@@ -97,6 +98,7 @@ nav:
   - Defaults: 050_defaults/exercise.md
   - Artifacts: 060_artifacts/exercise.md
   - Job Dependencies: 065_job_dependencies/exercise.md
+  - Schedules: 070_schedules/exercise.md
   - Unit Tests: 090_unit_tests/exercise.md
 - Advanced:
   - Environments: 100_environments/exercise.md

160_gitlab_ci/000_rollout/exercise_project.md

@@ -9,9 +9,9 @@ Your instance of Visual Studio Code is provisioned with your credentials to allo
 
 ## Task 2: Pulling from the upstream repository
 
-XXX
+The local clone of the `demo` project is configured with a remote pointing to the location of [the original project on GitHub](https://github.com/nicholasdille/container-slides). This is prepared in case the instructor needs to fix a demo. Let's test this safeguard:
 
 1. Open a terminal
 1. Change to the `demo` project directory
 1. List remotes: `git remote -v`
-1. Pull from the upstream repository: `git pull upstream --all`
+1. Pull from the upstream repository: `git pull upstream`

160_gitlab_ci/000_rollout/slides.md

@@ -6,60 +6,10 @@
 
 ---
 
-## GitLab
+## Environment
 
-Deploy a containerized stack for this workshop
+Containerized service stack for this workshop
 
-![](160_gitlab_ci/000_rollout/stack.drawio.svg) <!-- .element: style="width: 95%" -->
+![](160_gitlab_ci/000_rollout/stack.drawio.svg) <!-- .element: style="width: 90%; margin-top: 1em;" -->
 
-Obviously GitLab <i class="fa-duotone fa-face-smile-wink fa-duotone-colors"></i>
-
-traefik routes requests to containers
-
----
-
-## Problems with credentials
-
-If your credentials are not working:
-
-1. Go to https://code.inmylab.de
-1. Click on "Show username and password"
-1. Authenticate using the user `seat` and your code
-
-The code was provided as part of your credentials:
-
-```plaintext
-code;hostname;username;password
-ABCDE;seatN.inmylab.de;seatN;0123456789abcdef0123456789abcdef
-```
-
-OR
-
-```plaintext
-Host seatN.vscode.inmylab.de
-User seatN
-Code ABCDE
-Password 0123456789abcdef0123456789abcdef
-```
-
----
-
-## Code
-
-The source for the slides as well as the demos are located in my repository called [container-slides](https://github.com/nicholasdille/container-slides)
-
-Please refer to the release matching the date of your workshop
-
-You should use the release tag to access the files in the repository
-
-The hands-on chapters have a link to the exact directory in the repository
-
-### Demos tell a story
-
-Demos focus on a single feature
-
-Each demo improves the previous state
-
-All demos will have unanswered questions
-
-Following demos will again improve
+See [introduction](/hands-on/2023-11-30/)

160_gitlab_ci/010_jobs_and_stages/exercise.md

@@ -112,6 +112,8 @@ Afterwards check the pipeline in the GitLab UI. You should see a successful pipe
     Both jobs `lint` and `audit` must be in the stage `check`.
 
 ??? example "Solution (Click if you are stuck)"
+    `.gitlab-ci.yml`:
+    
     ```yaml linenums="1" hl_lines="5-17"
     stages:
     - check

160_gitlab_ci/020_variables/ci.md

@@ -10,9 +10,7 @@ Available in project-, group- and instance-level
 
 Careful with protected variables
 
----
-
-## Hands-On
+### Hands-On
 
 See chapter [Variables](/hands-on/20231130/020_variables/exercise/)
 

160_gitlab_ci/020_variables/exercise.md

@@ -30,6 +30,8 @@ Afterwards check the pipeline in the GitLab UI. You should see a successful pipe
     2. Replace the build command with the one provided above
 
 ??? example "Solution (Click if you are stuck)"
+    `.gitlab-ci.yml`:
+
     ```yaml linenums="1" hl_lines="21-22 26-30"
     stages:
     - check
@@ -79,6 +81,8 @@ Afterwards check the pipeline in the GitLab UI. You should see a successful pipe
     2. Replace the variable `${version}` with the predefined variable `${CI_COMMIT_REF_NAME}`
 
 ??? example "Solution (Click if you are stuck)"
+    `.gitlab-ci.yml`:
+    
     ```yaml linenums="1" hl_lines="25-28"
     stages:
     - check
@@ -137,6 +141,8 @@ Afterwards check the pipeline in the GitLab UI. You should see a successful pipe
     The `-ldflags` option needs to be extended with `-X 'main.Author=${AUTHOR}'`
 
 ??? example "Solution (Click if you are stuck)"
+    `.gitlab-ci.yml`:
+    
     ```yaml linenums="1" hl_lines="25-28"
     stages:
     - check
@@ -172,3 +178,7 @@ Afterwards check the pipeline in the GitLab UI. You should see a successful pipe
     If you want to jump to the solution, execute the following command:
 
     git checkout origin/160_gitlab_ci/020_variables/ci -- '*'
+
+<!-- TODO: masked variables -->
+
+<!-- TODO: protected variables -->

160_gitlab_ci/020_variables/slides.md

@@ -14,8 +14,6 @@ Variables [](https://docs.gitlab.com/ee/ci/yaml/#variables) can be...
 - predefined by GitLab
 - defined in the UI
 
----
-
-## Hands-On
+### Hands-On
 
 See chapter [Variables](/hands-on/20231130/020_variables/exercise/)

160_gitlab_ci/030_script_blocks/exercise.md

@@ -18,6 +18,8 @@ Afterwards check the pipeline in the GitLab UI. You should see a successful pipe
     Move calls to `apk` to the `before_script`.
 
 ??? example "Solution (Click if you are stuck)"
+    `.gitlab-ci.yml`:
+    
     ```yaml linenums="1" hl_lines="7-9 15-17 23-25"
     stages:
     - check

160_gitlab_ci/040_image/exercise.md

@@ -4,23 +4,23 @@
     Learn how to...
 
     - specify which container image to use for a job
-    - XXX
+    - tailor the execution environment to your needs
 
 ## Task: Simplify using container images
 
 In the previous exampes, we called `apk` at the beginning of every job to install Go. This had to be repeated for every job because Go was not present. Choosing an image for a job using the `image` directive, time is saved by avoiding commands to install required tools. See the [official documentation](https://docs.gitlab.com/ee/ci/yaml/#image).
 
 Replace the calls to `apk` with the container image `golang:1.19.2`.
 
-XXX version bump for `golang` image
-
 Afterwards check the pipeline in the GitLab UI. You should see a successful pipeline run.
 
 ??? info "Hint (Click if you are stuck)"
     - Remove `before_script`
     - Add `image: golang:1.19.2` instead
 
 ??? example "Solution (Click if you are stuck)"
+    `.gitlab-ci.yml`:
+    
     ```yaml linenums="1" hl_lines="7 13 19"
     stages:
     - check

160_gitlab_ci/040_image/slides.md

@@ -18,8 +18,6 @@ Do not use community images
 
 Avoid maintaining custom image
 
----
-
-## Hands-On
+### Hands-On
 
 See chapter [Variables](/hands-on/20231130/040_image/exercise/)