Update automation lecture for wt2425

Author: MakisH

05_testing_and_ci/automation_exercise.md

@@ -2,11 +2,13 @@
 
 In this exercise, we create automated workflows and pipelines based on GitHub Actions. We are again working with our beloved diffusion Python code.
 
-Deadline: **Thursday, February 2nd, 2023, 09:00**
+Deadline: **Thursday, January 29th, 2025, 09:00**
 
 ## Preparations
 
-Import the [automation exercise repository](https://github.com/Simulation-Software-Engineering/automation-exercise-wt2223) in your own account/namespace on GitHub and name it `automation-exercise` again. **Note**: We cannot work with forks here because GitHub Actions may not work in pull requests without explicit approval of the owner of the target repository
+Import the [automation exercise repository](https://github.com/Simulation-Software-Engineering/automation-exercise-wt2425) in your own account/namespace on GitHub and name it `automation-exercise`. It is also easier to add badges (see below) to the `README.md` if the repository is under your control.
+
+**Note**: We cannot work with forks here because GitHub Actions may not work in pull requests without explicit approval of the owner of the target repository
 
 ## Task descriptions
 
@@ -24,12 +26,12 @@ Once the workflow runs successfully, add a [GitHub workflow status badge](https:
 
 ## Submission
 
-- Submit your solution via an issue in the *upstream* [automation exercise repository](https://github.com/Simulation-Software-Engineering/automation-exercise-wt2223). The issue should be named `[USERNAME] Automation exercise`, e.g., `[uekermbn] Automation exercise`. Please use your GitLab username here. Add a link to your GitHub repository in the issue. If necessary, add further explanations in the issue description.
+- Submit your solution via an issue in the *upstream* [automation exercise repository](https://github.com/Simulation-Software-Engineering/automation-exercise-wt2425). The issue should be named `[USERNAME] Automation exercise`, e.g., `[uekermbn] Automation exercise`. Please use your GitLab username here. Add a link to your GitHub repository in the issue. If necessary, add further explanations in the issue description.
 
 ## Bonus: GitLab CI/CD
 
 Realize the same workflows in GitLab CI/CD :)
 
 - Create a new project under your namespace and push your existing automation repository to this remote.
 - Create a VM on [bwCloud](https://www.bw-cloud.org/) and create a GitLab Runner with a Docker executor there. Register the runner in your repository.
-- Add a link to this repository in the submission issue above and, if necessary, explain what you did. Be sure that your repository is visible to us (either public or add `uekermbn`).
+- Add a link to this repository in the submission issue above and, if necessary, explain what you did. Be sure that your repository is visible to us (either public or add `gchourdakis`).

05_testing_and_ci/automation_slides.md

@@ -64,8 +64,10 @@ slideOptions:
 
 - Check code formatting and quality
 - Compile and test code for different platforms
-- Generate coverage reports and visualization
+- Periodically run tasks
+    - Big tests, nightly builds...
 - Build documentation and deploy it
+- Generate coverage reports and visualization
 - Build, package, and upload releases
 
 ---

05_testing_and_ci/github_actions_demo.md

@@ -2,7 +2,7 @@
 
 ## 1. Setting up a Test Job
 
-- Clone [automation lecture repository](https://github.com/Simulation-Software-Engineering/automation-lecture-wt2223) and run code and tests
+- Clone [automation lecture repository](https://github.com/Simulation-Software-Engineering/automation-lecture-wt2425) and run code and tests
 - Set up workflow file
 
   ```bash
@@ -107,12 +107,12 @@
 ## 3. Other Workflows
 
 - Show workflows of [preCICE](https://github.com/precice/precice)
-    - Show `Actions` tab
-        - `Build and test` job, click on a run
-        - Jobs created through test matrix
-        - Click on a job, click on a few steps
-    - Show `workflows` folder, click on `Build and Test`
-    - Only one job. `build`, `test`, ... are modeled as steps
+  - Show `Actions` tab
+    - `Build and test` job, click on a run
+    - Jobs created through test matrix
+    - Click on a job, click on a few steps
+  - Show `workflows` folder, click on `Build and Test`
+  - Only one job. `build`, `test`, ... are modeled as steps
 
 ## 4. act Demo
 

05_testing_and_ci/github_actions_slides.md

@@ -69,7 +69,7 @@ From: [https://docs.github.com/en/actions](https://docs.github.com/en/actions)
 
 ## Components (2/2)
 
-<img src="https://docs.github.com/assets/cb-25628/images/help/images/overview-actions-simple.png" width=95%; style="margin-left:auto; margin-right:auto; padding-top: 25px; padding-bottom: 25px; background: #eeeeee">
+<img src="https://docs.github.com/assets/cb-25535/mw-1440/images/help/actions/overview-actions-simple.webp" width=95%; style="margin-left:auto; margin-right:auto; padding-top: 25px; padding-bottom: 25px; background: #eeeeee">
 
 
 From [GitHub Actions tutorial](https://docs.github.com/en/actions)
@@ -78,7 +78,7 @@ From [GitHub Actions tutorial](https://docs.github.com/en/actions)
 
 ## Setting up a Workflow
 
-- Workflow file files stored `${REPO_ROOT}/.github/workflows`
+- Workflow files stored in `${REPO_ROOT}/.github/workflows`
 - Configured via YAML file
 
 ```yaml
@@ -198,7 +198,7 @@ steps:
 
   ```yaml
   - name: "Upload artifact"
-    uses: actions/upload-artifact@v2
+    uses: actions/upload-artifact@v4
     with:
       name: my-artifact
       path: my_file.txt
@@ -238,13 +238,14 @@ steps:
 ## Demo: GitHub Actions
 
 - Set up simple CI pipeline using GitHub Actions
-- Reuse code of Python testing lecture
 - Pipeline has three steps
 
     1. Check formatting
     2. Build application
     3. Test application
 
+- Reusing code of Python testing lecture
+
 ---
 
 ## Advanced Topics

05_testing_and_ci/gitlab_ci_demo.md

@@ -1,6 +1,6 @@
 # Demo: GitLab Runner
 
-Test code in [automation lecture repository](https://gitlab-sim.informatik.uni-stuttgart.de/simulation-software-engineering-wite2223/lecture-automation) on our GitLab instance
+Test code in [automation lecture repository](https://gitlab-sim.informatik.uni-stuttgart.de/simulation-software-engineering-wite2425/lecture-automation) on our GitLab instance
 
 ## Inspect Repository
 

05_testing_and_ci/gitlab_ci_slides.md

@@ -56,7 +56,7 @@ From: [https://docs.gitlab.com/ee/ci/](https://docs.gitlab.com/ee/ci/)
     - Jobs in one stage my be executed in parallel
 - Stages: Group jobs and determine running order
 - [Runner](https://docs.gitlab.com/runner/): Server that runs jobs
-- [Artifacts](https://docs.gitlab.com/ee/ci/pipelines/job_artifacts.html): Files to be shared between jobs or to be kept after workflow finishes
+- [Artifacts](https://docs.gitlab.com/ee/ci/jobs/job_artifacts.html): Files to be shared between jobs or to be kept after workflow finishes
 - No "Actions", but instead integrated features
     - Repository checked out by default
     - Handling of artifacts integrated
@@ -191,11 +191,10 @@ deploy job:
 
 - Complex pipelines, e.g.,
     - [Directed Acyclic Graph](https://docs.gitlab.com/ee/ci/directed_acyclic_graph/)
-    - [Multi-project pipelines](https://docs.gitlab.com/ee/ci/pipelines/multi_project_pipelines.html)
-    - [Parent-child pipelines](https://docs.gitlab.com/ee/ci/pipelines/parent_child_pipelines.html)
+    - [Multi-project pipelines](https://docs.gitlab.com/ee/ci/pipelines/downstream_pipelines.html#multi-project-pipelines)
 - [Anchors](https://docs.gitlab.com/ee/ci/yaml/yaml_optimization.html#anchors)
 - [ChatOps](https://docs.gitlab.com/ee/ci/chatops/)
-- [Extended testing](https://docs.gitlab.com/ee/ci/unit_test_reports.html)
+- [Extended testing](https://docs.gitlab.com/ee/ci/testing/unit_test_reports.html)
 
 ---