Update URLs and paths to refer this repository (#16)

Author: kangasta

docs/examples/jenkins/ansible-kubernetes/Jenkinsfile

@@ -1,3 +1,5 @@
+String d = "docs/examples/jenkins/ansible-kubernetes"
+
 pipeline {
     agent any
     parameters {
@@ -7,22 +9,19 @@ pipeline {
         stage("deploy") {
             agent {
                 dockerfile {
-                    dir "ansible-kubernetes"
+                    dir "$d"
                     reuseNode true
                 }
             }
             environment {
                 K8S_AUTH_KUBECONFIG = credentials('kubeconfig')
+                KUBECONFIG = credentials('kubeconfig')
             }
             steps {
                 sh """
-                    ansible-playbook ansible-kubernetes/deploy-to-kubernetes.yml --extra-vars "animal=${params.ANIMAL}"
+                    ansible-playbook $d/deploy-to-kubernetes.yml --extra-vars "animal=${params.ANIMAL}"
+                    ./$d/wait-until-service-up.sh
                 """
-                // Do not use Groovy string interpolation for credential
-                sh '''
-                    export KUBECONFIG=$K8S_AUTH_KUBECONFIG
-                    ./ansible-kubernetes/wait-until-service-up.sh
-                '''
             }
         }
     }

docs/examples/jenkins/ansible-kubernetes/README.md

@@ -23,7 +23,7 @@ In the _New credentials_ form:
 
 First, create a new pipeline via [New Item](http://localhost:8080/view/all/newJob) button in the rigth side menu of the Jenkins dashboard. The name of the pipeline could be for example `Animals` and it should be an pipeline.
 
-In the configure pipeline view, scroll to the bottom and under Pipeline sub-header select `Pipeline script from SCM`. SCM type should be `Git` and Repository URL the url of this repository: `https://github.com/kangasta/jenkins-examples.git`. Ensure that branch specifier includes `main` branch of the repository and modify the Script Path to be `ansible-kubernetes\Jenkinsfile`.
+In the configure pipeline view, scroll to the bottom and under Pipeline sub-header select `Pipeline script from SCM`. SCM type should be `Git` and Repository URL the url of this repository: `https://github.com/kangasta/cicd-examples.git`. Ensure that branch specifier includes `main` branch of the repository and modify the Script Path to be `docs/examples/jenkins/ansible-kubernetes/Jenkinsfile`.
 
 After you have created the pipeline, try to execute it by clicking _Build Now_. The pipeline should have deployed the example application into the Kubernetes cluster with the default image tag (`cow`) defined in the [deploy-to-kubernetes.yml](./deploy-to-kubernetes.yml) Ansible playbook.
 

docs/examples/jenkins/ansible-kubernetes/wait-until-service-up.sh

@@ -14,9 +14,9 @@ To run the job DSL script, create a new pipeline with following script as an inl
 
 ```groovy
 node {
-    git branch: 'main', url: 'https://github.com/kangasta/jenkins-examples.git'
-    jobDsl targets: 'build-status-pipelines/jobs.groovy'
+    git branch: 'main', url: 'https://github.com/kangasta/cicd-examples.git'
+    jobDsl targets: 'docs/examples/jenkins/build-status-pipelines/jobs.groovy'
 }
 ```
 
-The execution will likely fail with `ERROR: script not yet approved for use` message. To enable this script, navigate to [Manage Jenkins > In-process Script Approval](http://localhost:8080/scriptApproval/), inspect the script, and click Approve. Then try to run the created seed project again. It should now succeed and list the created resources.
+The execution will likely fail with `ERROR: script not yet approved for use` message. To enable this script, navigate to [Manage Jenkins > In-process Script Approval](http://localhost:8080/scriptApproval/), inspect the script, and click _Approve_. Then try to run the created seed project again. It should now succeed and list the created resources.

docs/examples/jenkins/build-status-pipelines/README.md

@@ -1,3 +1,5 @@
+String d = "docs/examples/jenkins/build-status-pipelines"
+
 folder('Status') {
     description('Example pipelines to produce success, unstable, failed, aborted, and not-built statuses.')
 }
@@ -9,7 +11,7 @@ for (status in statuses) {
     pipelineJob(name) {
         definition {
             cps {
-                script(readFileFromWorkspace("build-status-pipelines/${status.toLowerCase()}.Jenkinsfile"))
+                script(readFileFromWorkspace("$d/${status.toLowerCase()}.Jenkinsfile"))
                 sandbox()
             }
         }
@@ -20,7 +22,7 @@ for (status in statuses) {
 pipelineJob('Status/Not built') {
     definition {
         cps {
-            script(readFileFromWorkspace("build-status-pipelines/success.Jenkinsfile"))
+            script(readFileFromWorkspace("$d/success.Jenkinsfile"))
             sandbox()
         }
     }

docs/examples/jenkins/build-status-pipelines/jobs.groovy

@@ -1,3 +1,5 @@
+String d = "docs/examples/jenkins/parallel-robot-pipeline"
+
 pipeline {
     agent any
     parameters {
@@ -11,24 +13,24 @@ pipeline {
             parallel {
                 stage('Chromium') {
                     agent { docker {
-                        image 'ghcr.io/kangasta/robot-selenium-chromium:latest'
+                        image 'ghcr.io/kangasta/robot-browser:latest'
                         args '--entrypoint=""'
                         reuseNode true
                     } }
                     steps {
-                        sh "robot -d robot_output -l none -r none -o chromium.xml -N Chromium -v URL:${params.URL} --nostatusrc parallel-robot-pipeline/suites/"
+                        sh "robot -d robot_output -l none -r none -o chromium.xml -N Chromium -v URL:${params.URL} --nostatusrc $d/suites/"
                         // If reuseNode true was not used, we would have to stash the output XML.
                         // stash includes: 'robot_output/**', name: 'Chromium'
                     }
                 }
                 stage('Firefox') {
                     agent { docker {
-                        image 'ghcr.io/kangasta/robot-selenium-firefox:latest'
+                        image 'ghcr.io/kangasta/robot-browser:latest'
                         args '--entrypoint=""'
                         reuseNode true
                     } }
                     steps {
-                        sh "robot -d robot_output -l none -r none -o b.xml -N Firefox -v URL:${params.URL} --nostatusrc parallel-robot-pipeline/suites/"
+                        sh "robot -d robot_output -l none -r none -o b.xml -N Firefox -v URL:${params.URL} --nostatusrc $d/suites/"
                         // If reuseNode true was not used, we would have to stash the output XML.
                         // stash includes: 'robot_output/**', name: 'Firefox'
                     }
@@ -37,18 +39,15 @@ pipeline {
         }
         stage('Process logs') {
             agent { docker {
-                image 'ghcr.io/kangasta/robot-selenium-firefox:latest'
+                image 'ghcr.io/kangasta/robot-browser:latest'
                 args '--entrypoint=""'
                 reuseNode true
             } }
             steps {
                 // If reuseNode true was not used, we would have to unstash the output XMLs.
                 // unstash 'Chromium'
                 // unstash 'Firefox'
-                sh """
-                    rebot -d rebot_output -o output.xml -N '${env.JOB_BASE_NAME} ${BUILD_DISPLAY_NAME}' --nostatusrc robot_output/*.xml
-                    cp -r robot_output/*_screenshots rebot_output/ || true # Do not fail the pipeline if no screenshot are available
-                """
+                sh "rebot -d rebot_output -o output.xml -N '${env.JOB_BASE_NAME} ${BUILD_DISPLAY_NAME}' --nostatusrc robot_output/*.xml"
             }
         }
     }

docs/examples/jenkins/parallel-robot-pipeline/Jenkinsfile

@@ -10,11 +10,11 @@ In order to be able to run the pipeline we will need [Docker Pipeline](https://p
 
 ## Configure the pipeline
 
-First, create a new pipeline via [New Item](http://localhost:8080/view/all/newJob) button in the rigth side menu of the Jenkins dashboard. The name of the pipeline could be for example `Screenshots` and it should be an pipeline.
+First, create a new pipeline via _[New Item](http://localhost:8080/view/all/newJob)_ button in the rigth side menu of the Jenkins dashboard. The name of the pipeline could be for example `Screenshots` and it should be an pipeline.
 
-In the configure pipeline view, scroll to the bottom and under Pipeline sub-header select `Pipeline script from SCM`. SCM type should be `Git` and Repository URL the url of this repository: `https://github.com/kangasta/jenkins-examples.git`. Ensure that branch specifier includes `main` branch of the repository and modify the Script Path to be `parallel-robot-pipeline/Jenkinsfile`.
+In the configure pipeline view, scroll to the bottom and under Pipeline sub-header select `Pipeline script from SCM`. SCM type should be `Git` and Repository URL the url of this repository: `https://github.com/kangasta/cicd-examples.git`. Ensure that branch specifier includes `main` branch of the repository and modify the Script Path to be `docs/examples/jenkins/parallel-robot-pipeline/Jenkinsfile`.
 
-After you have created the pipeline, try to execute it by clicking Build Now. All Robot Framework tasks should be in Skipped state as we did not specify URL variable, see `.robot` file for details. In addition, after the first execution Jenkins should have updated the project configuration to contain parameters defined in the pipeline and we can now pass target URL to our automation tasks in Build with Parameters menu.
+After you have created the pipeline, try to execute it by clicking _Build Now_. All Robot Framework tasks should be in Skipped state as we did not specify URL variable, see `.robot` file for details. In addition, after the first execution Jenkins should have updated the project configuration to contain parameters defined in the pipeline and we can now pass target URL to our automation tasks in Build with Parameters menu.
 
 Finally, If the robot log cannot be loaded after task execution, see [this stackoverflow post](https://stackoverflow.com/questions/36607394/error-opening-robot-framework-log-failed) for solution. To summarize, run following command in Jenkins Script Console to modify Jenkins servers Content Security Policy (CSP):