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/)

160_gitlab_ci/050_defaults/exercise.md

@@ -3,8 +3,8 @@
 !!! tip "Goal"
     Learn how to...
 
-    - Avoid repetition in jobs
-    - Specify defaults are the top of your pipeline
+    - avoid repetition in jobs
+    - specify defaults are the top of your pipeline
 
 ## Task: Don't repeat yourself
 
@@ -19,6 +19,8 @@ Afterwards check the pipeline in the GitLab UI. You should see a successful pipe
     1. Add `default` with the `image` directive at the top
 
 ??? example "Solution (Click if you are stuck)"
+    `.gitlab-ci.yml`:
+    
     ```yaml linenums="1" hl_lines="5-6"
     stages:
     - check
@@ -63,4 +65,7 @@ Jobs can still choose to use an image different from the default:
 
 ## Bonus 2: Default values for variables
 
-XXX `variables` outside `default`
+See the official documentation for [`default`](https://docs.gitlab.com/ee/ci/yaml/#default) as well as [`variables`](https://docs.gitlab.com/ee/ci/yaml/#variables) and check how they are related.
+
+??? example "Solution (Click if you are stuck)"
+    Global variables are not located under `default` but under the global `variables` keyword.

160_gitlab_ci/050_defaults/slides.md

@@ -17,8 +17,6 @@ Apply settings to all jobs using `default` [](https://docs.gitlab.com/ee/ci/yaml
 - `after_script`
 - and some more we will explore later <i class="fa-duotone fa-face-smile-halo fa-duotone-colors"></i>
 
----
-
-## Hands-On
+### Hands-On
 
 See chapter [Variables](/hands-on/20231130/050_defaults/exercise/)

160_gitlab_ci/060_artifacts/exercise.md

@@ -31,6 +31,8 @@ Afterwards check the pipeline in the GitLab UI. You should see a successful pipe
     ```
 
 ??? example "Solution (Click if you are stuck)"
+    `.gitlab-ci.yml`:
+    
     ```yaml linenums="1" hl_lines="4 27-35"
     stages:
     - check
@@ -75,11 +77,13 @@ Afterwards check the pipeline in the GitLab UI. You should see a successful pipe
 
 ## Bonus 1: Define from which jobs to receive artifacts
 
-Usually, artifacts are received from all job in the previous stages. Decide from which jobs to receive artifacts using the `dependencies` directive. See the [official documentation](https://docs.gitlab.com/ee/ci/yaml/#dependencies).
+Usually, artifacts are received from all jobs in the previous stages. Decide from which jobs to receive artifacts using the `dependencies` keyword. See the [official documentation](https://docs.gitlab.com/ee/ci/yaml/#dependencies).
 
-XXX
+Modify the job `test` to consume artifacts only from the job `build`.
 
 ??? example "Solution (Click if you are stuck)"
+    `.gitlab-ci.yml`:
+    
     ```yaml linenums="1" hl_lines="34-35"
     stages:
     - check
@@ -122,7 +126,9 @@ XXX
 
 ## Bonus 2: Passing environment variables
 
-XXX https://docs.gitlab.com/ee/ci/variables/index.html#pass-an-environment-variable-to-another-job
+In some situations, artifacts are to heavy-weight and passing a variable would be enough. Read the documentation for [passing environment variables](https://docs.gitlab.com/ee/ci/variables/index.html#pass-an-environment-variable-to-another-job) and implement this between two jobs of your choice.
+
+The following hint and solution are a working example.
 
 ??? info "Hint (Click if you are stuck)"
     Example for creating an artifact for environment variables:
@@ -137,6 +143,8 @@ XXX https://docs.gitlab.com/ee/ci/variables/index.html#pass-an-environment-varia
     ```
 
 ??? example "Solution (Click if you are stuck)"
+    `.gitlab-ci.yml`:
+    
     ```yaml linenums="1" hl_lines="21-22 27 29 33-34 40"
     stages:
     - check

160_gitlab_ci/060_artifacts/slides.md

@@ -63,60 +63,6 @@ See GitLab API [](https://docs.gitlab.com/ee/api/job_artifacts.html#download-the
 
 ---
 
-## Job dependencies using `needs` 1/
-
-`needs` [](https://docs.gitlab.com/ee/ci/yaml/#needs) can start jobs from the next stage early...
-
-```yaml
-job1:
-  stage: stage1
-  #...
-job2:
-  stage: stage2
-  needs: job1
-  #...
-```
-
-...or delay them in the same stage
-
-```yaml
-job1:
-  stage: test
-  #...
-job2:
-  stage: test
-  needs: job1
-  #...
-```
-
----
-
-## Job dependencies using `needs` 2/2
-
-Depend on a job but do not consume artifacts [](https://docs.gitlab.com/ee/ci/yaml/#needsartifacts):
-
-```yaml
-job_name:
-  #...
-
-job_name2:
-  needs:
-    job: job_name
-    artifacts: false
-```
-
-Consume artifacts from parent (upstream) pipeline [](https://docs.gitlab.com/ee/ci/yaml/#needspipelinejob):
-
-```yaml
-job_name:
-  script: cat artifact.txt
-  needs:
-    - pipeline: $PARENT_PIPELINE_ID
-      job: create-artifact
-```
-
----
-
 ## Pro tip: When variables are enough
 
 Passing variables between jobs **is** possible (since GitLab 12.9)

160_gitlab_ci/065_job_dependencies/exercise.md

@@ -3,18 +3,18 @@
 !!! tip "Goal"
     Learn how to...
 
-    - XXX
+    - ignore stages
+    - start jobs as soon as dependencies are met
 
-## Task: Start the build job early
+## Task: Start a job early
 
-XXX start `build` after `audit` without waiting for `lint`
+Start the job `build` as soon as the job `audit` completes without waiting for other job of the stage `check` to finish. Check out the official documentation of [`needs`](https://docs.gitlab.com/ee/ci/yaml/#needs).
 
 Afterwards check the pipeline in the GitLab UI. You should see a successful pipeline run.
 
-??? info "Hint (Click if you are stuck)"
-    XXX
-
 ??? example "Solution (Click if you are stuck)"
+    `.gitlab-ci.yml`:
+
     ```yaml linenums="1" hl_lines="21-22"
     stages:
     - check
@@ -57,16 +57,15 @@ Afterwards check the pipeline in the GitLab UI. You should see a successful pipe
 
 This was just a demonstration. The changes will not be preserved in the following chapters.
 
-## Bonus: Start the lint job late
+## Bonus: Start a job late
 
-XXX start `lint` after `audit`
+If two jobs in the same stage should not be executed at the same time, the [`needs`](https://docs.gitlab.com/ee/ci/yaml/#needs) keyword can also delay a job until the dependencies are met. Modify the job `lint` so that it waits for the job `audit` to finish.
 
 Afterwards check the pipeline in the GitLab UI. You should see a successful pipeline run.
 
-??? info "Hint (Click if you are stuck)"
-    XXX
-
 ??? example "Solution (Click if you are stuck)"
+    `.gitlab-ci.yml`:
+    
     ```yaml linenums="1" hl_lines="11-12"
     stages:
     - check