small updates

puzzle · Sep 25, 2023 · 06d27ec · 06d27ec
1 parent e01a5c8
commit 06d27ec
Show file tree

Hide file tree

Showing 6 changed files with 9 additions and 6 deletions.
diff --git a/content/en/docs/04/tooling_images.md b/content/en/docs/04/tooling_images.md
@@ -81,7 +81,7 @@ Starting a Gradle Daemon (subsequent builds will be faster)
 > Task :compileJava
 > Task :processResources
 > Task :classes
-> Task :bootJarMainClassName
+> Task :resolveMainClassName
 > Task :bootJar
 > Task :jar
 > Task :assemble

diff --git a/content/en/docs/05/variables.md b/content/en/docs/05/variables.md
@@ -4,16 +4,17 @@ weight: 5
 sectionnumber: 5
 ---
 
-In GitLab CI/CD, variables can be used to customize jobs by defining and storing values. When using variables there is no need to hard code values. In GitLab, CI/CD variables can be defined by going to `Settings` --> `CI/CD` --> `Variables`  or by simply defining them in the .gitlab-ci.yml file.
-
-![GitLab Variables](../variable.png)
+In GitLab CI/CD, variables can be used to customize jobs by defining and storing values. When using variables there is no need to hard code values.
+In GitLab, CI/CD variables can be defined by going to `Settings` --> `CI/CD` --> `Variables`  or by simply defining them in the .gitlab-ci.yml file.
 
 Variables are useful for configuring third-party services for different environments, such as testing, staging, production, etc. Modify the services attached to those environments by simply changing the variable that points to the API endpoint the services need to use. Also use variables to configure jobs and then make them available as environment variables within the jobs when they run.
 
 As pointed out before, you can define variables in your `gitlab-ci.yml`. You can reuse this variable within your pipeline across different jobs and stages.
 
 If you want to reuse a variable across different Projects or Groups, you can define them through your GitLab instance (`Settings` --> `CI/CD` --> `Variables`)
 
+![GitLab Variables](../variable.png)
+
 In this lab we will talk about the variables in the `gitlab-ci.yml` file only.
 
 {{% alert color="primary" %}}

diff --git a/content/en/docs/09/job_control.md b/content/en/docs/09/job_control.md
@@ -29,6 +29,8 @@ Use `except` to define when a job does not run.
 
 Use the `only:refs` and `except:refs` keywords to control when to add jobs to a pipeline based on branch names or pipeline types.
 
+{{% alert title="Warning" color="secondary" %}}`only` and `except` are not being actively developed. To control when to add jobs to pipelines, use rules instead.
+{{% /alert %}}
 
 ## {{% param sectionnumber %}}.2: Execution control
 

diff --git a/content/en/docs/11/security.md b/content/en/docs/11/security.md
@@ -81,7 +81,7 @@ Now the pipeline should fail because the GitLab Secret Analyzer will find a priv
 
 ![security_pipeline_fail](../security_pipeline_fail.png)
 
-Here you see the failed pipeline. By clicking ⋮ on the right side you can download the job artifacts. To get the report of the failed job, click on `Download secret_detection_default_branch:secret_detection artifact`. We will learn more on artifacts in the next lab.
+Here you see the failed pipeline. By clicking the download menu ⍗ on the right side you can download the job artifacts. To get the report of the failed job, click on `Download artifacts` and `secret_detection_default_branch:secret_detection`. We will learn more on artifacts in the next lab.
 
 {{% alert title="Warning" color="secondary" %}}If you ever push a secret into a repository, **YOU MUST CONSIDER THIS SECRET AS INSECURE**. Remove the secret from the repository and change all related secrets!{{% /alert %}}
 

diff --git a/content/en/docs/11/security_pipeline_fail.png b/content/en/docs/11/security_pipeline_fail.png
diff --git a/content/en/docs/12/artifacts.md b/content/en/docs/12/artifacts.md
@@ -64,7 +64,7 @@ Click on `Download` to get the Trivy report file and open it to see the report.
 
 ## Task {{% param sectionnumber %}}.3: Pipeline Artifacts Lab
 
-Go to your pipeline `Build` --> `Pipelines` and click on the ⋮ to see the downloadable artifacts.
+Go to your pipeline `Build` --> `Pipelines` and click on the download menu ⍗ to see the downloadable artifacts.
 
 Then download them and open the JUnit test report.