Filled many open spots after 20241112

Author: nicholasdille

160_gitlab_ci/000_rollout/vscode/vscode/Dockerfile

@@ -25,7 +25,8 @@ curl -sLf https://github.com/uniget-org/cli/releases/latest/download/uniget_linu
 uniget install \
     gojq \
     go \
-    glab
+    glab \
+    gitlabci-local
 EOF
 
 COPY --chmod=0755 git.sh /opt/entrypoint.d/

160_gitlab_ci/065_job_dependencies/slides.md

@@ -66,6 +66,8 @@ See chapter [Job dependencies](/hands-on/2024-11-12/065_job_dependencies/exercis
 
 ---
 
-## Pro tip: XXX
+## Pro tip: Passing atifacts with `needs`
 
-One stage with two jobs and `needs` -> artifacts work
+If you have one stage with two jobs where one depends on the other using `needs`, artifacts are passed correctly between them.
+
+This is important to note because without `needs` jobs in the same stage to not receive artifacts from each other.

160_gitlab_ci/120_templates/exercise.md

@@ -14,7 +14,7 @@ Create a template for compiling a go binary from the job `build` and use it in t
 Afterwards check the pipeline in the GitLab UI. You should see a successful pipeline run.
 
 ??? info "Hint (Click if you are stuck)"
-    XXX
+    `.gitlab-ci.yml`:
 
     ```yaml
     .build-go:

160_gitlab_ci/130_rules/slides.md

@@ -109,12 +109,11 @@ Template to disable job:
 
 ## Pro tip: Fields for rules
 
-XXX variables [](https://docs.gitlab.com/ee/ci/yaml/#rulesvariables)
+Rules not only control execution of jobs but can also configure jobs through the use of the following fields:
 
-XXX variable precedence
+- Add additional `variables` [](https://docs.gitlab.com/ee/ci/yaml/#rulesvariables) to customize the behaviour of the job
+- Limit a rule to changes `changes` [](https://docs.gitlab.com/ee/ci/yaml/#ruleschanges) on specific files
+- Execute a job only if a specific file `exists` [](https://docs.gitlab.com/ee/ci/yaml/#rulesexists)
+- Make a job dependent on other jobs using `needs` [](https://docs.gitlab.com/ee/ci/yaml/#rulesneeds)
 
-XXX changes [](https://docs.gitlab.com/ee/ci/yaml/#ruleschanges)
-
-XXX exists [](https://docs.gitlab.com/ee/ci/yaml/#rulesexists)
-
-XXX needs [](https://docs.gitlab.com/ee/ci/yaml/#rulesneeds)
+Rules become especially powerful when combining the fields supported by rules - including `if`

160_gitlab_ci/255_troubleshooting/exercise.md

@@ -1,18 +1,55 @@
 # Troubleshooting
 
 !!! tip "Goal"
-    Learn how to...
-
-    - XXX
+    Learn how to run a pipeline locally
 
 ## Preparation
 
-XXX
+Open a terminal and make sure the working directory is your repository.
+
+## Task 1: Run a single job
 
-## Task: Use gcil
+Select a single job to run:
 
 ```shell
 gcil
-gcil -p
-gcil -l
 ```
+
+## Task 2: Run the whole pipeline
+
+Run the whole pipeline:
+
+```shell
+gcil --pipeline
+```
+
+## Task 3: Explore pre-defined variables
+
+Add a job to print all environment variables.
+
+??? info "Hint (Click if you are stuck)"
+    Use the following command to show all environment variables: `printenv | sort`
+
+??? example "Solution (Click if you are stuck)"
+
+    ```yaml
+    #...
+    new_job:
+    stage: check
+    script: |
+        printenv | sort
+    #...
+    ```
+
+## Task 4: Pass variables to the pipeline
+
+Check the help how to pass a variable called `AUTHOR` with a value of your choice.
+
+??? info "Hint (Click if you are stuck)"
+    The parameter `-e` is used to pass variables to the pipeline.
+
+??? example "Solution (Click if you are stuck)"
+
+    ```shell
+    gcil --pipeline --pipeline -e FOO=bar
+    ```

160_gitlab_ci/255_troubleshooting/slides.md

@@ -30,9 +30,17 @@ Use `command || true` is dangerous because it hides errors
 
 ## Shotgun debugging
 
-XXX many echos
+Adding many `echo` stagements is the most prominent (and hated) approach
 
-XXX if then else
+Better add regular output to the script blocks...
+
+...especially when using multi-line commands
+
+Add output to both branches of `if-then-else` statements
+
+Consider moving commands to a script file...
+
+...this can enable local debugging
 
 ---
 
@@ -44,7 +52,7 @@ Run whole pipelines locally using `gcil` (formerly `gitlabci-local`) [](https://
 
 Supports shell and Docker executor
 
-XXX
+Runs one or more jobs or even the whole pipeline
 
 ### ~~gitlab-runner~~
 

160_gitlab_ci/260_runners/slides.md

@@ -93,7 +93,15 @@ All features work across different runners
 
 ## Pro tip: Finding existing runners
 
-XXX
+No single place to discover runners
+
+See the CI/CD settings in the runner section
+
+Applies to groups and projects
+
+The list shows runners available
+
+Offers the option to disable instance runners
 
 ---
 

160_gitlab_ci/265_caches/slides.md

@@ -34,14 +34,18 @@ See chapter [caches](/hands-on/2024-11-12/265_caches/exercise/)
 
 ## Pro tip: Clear the cache
 
-XXX [](https://docs.gitlab.com/ee/ci/caching/#clearing-the-cache)
+Clear the cache [](https://docs.gitlab.com/ee/ci/caching/#clearing-the-cache) in two ways:
+
+1. Change the cache key in your pipeline
+1. On the pipeline page, click `Clear runner caches` in the upper right corner
 
 ---
 
 ## Pro tip 2: Runner local cache
 
-XXX [](https://docs.gitlab.com/ee/ci/caching/#where-the-caches-are-stored)
+For some executors, the runner stores the cache locally [](https://docs.gitlab.com/ee/ci/caching/#where-the-caches-are-stored) when not configured otherwise
 
-Shell: /home/gitlab-runner/cache/<user>/<project>/<cache-key>/cache.zip
+The local cache is located in the following directories:
 
-Docker: /var/lib/docker/volumes/<volume-id>/_data/<user>/<project>/<cache-key>/cache.zip
+- Shell: `/home/gitlab-runner/cache/<user>/<project>/<cache-key>/cache.zip`
+- Docker: `/var/lib/docker/volumes/<volume-id>/_data/<user>/<project>/<cache-key>/cache.zip`

160_gitlab_ci/320_secure_files/exercise.md

@@ -3,11 +3,16 @@
 !!! tip "Goal"
     Learn how to...
 
-    - XXX
+    - Upload secure files
+    - Use secure files in a job
 
 !!! tip "Hints"
     [Official documentation](https://docs.gitlab.com/ee/ci/secure_files/) for Secure Files
 
-## Task: XXX
+## Task 1: Upload a secure file
+
+XXX
+
+## Task 2: Use the secure file
 
 XXX

160_gitlab_ci/320_secure_files/slides.md

@@ -2,14 +2,57 @@
 
 <i class="fa-duotone fa-box-open-full fa-8x fa-duotone-colors" style="float: right; color: grey;"></i>
 
-## Secure Files
+## Secure Files (experimental)
 
 ---
 
-## Secure Files
+## Secure Files (experimental)
 
 <i class="fa-duotone fa-solid fa-4x fa-sparkles"></i> <!-- .element: style="float: right;" -->
 
-XXX [](https://docs.gitlab.com/ee/ci/secure_files/)
+Secure files [](https://docs.gitlab.com/ee/ci/secure_files/) are encrypted at rest
 
-XXX [](https://gitlab.com/gitlab-org/incubation-engineering/mobile-devops/download-secure-files)
+Each secure file is encrypted with a unique key...
+
+...and a SHA256 hash is stored in the database
+
+Up to 100 files and up to 5MB per file
+
+Binary files are supported
+
+Stored outside the repository and are not version controlled
+
+### Upload
+
+Either through the UI [](https://docs.gitlab.com/ee/ci/secure_files/#add-a-secure-file-to-a-project)
+
+Or through the API [](https://docs.gitlab.com/ee/api/secure_files.html)
+
+The Developer role is required to access secure files
+
+---
+
+## Secure Files (experimental)
+
+### Use secure files
+
+Downloading secure files in a pipeline requires a binary [](https://gitlab.com/gitlab-org/incubation-engineering/mobile-devops/download-secure-files)
+
+Environment variable `SECURE_FILES_DOWNLOAD_PATH` defines where files should be downloaded to
+
+```yaml
+test:
+  variables:
+    SECURE_FILES_DOWNLOAD_PATH: './where/files/should/go/'
+  script: |
+    curl \
+        --silent \
+        --url "https://gitlab.com/gitlab-org/incubation-engineering/mobile-devops/download-secure-files/-/raw/main/installer" \
+    | bash
+```
+
+---
+
+## Hands-On
+
+See chapter [Secure Files](/hands-on/2024-11-12/320_secure_files/exercise/)