You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: examples/jenkins/ansible-kubernetes/index.html
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -679,7 +679,7 @@ <h2 id="preparing-the-jenkins-instance">Preparing the Jenkins instance</h2>
679
679
</ol>
680
680
<h2id="configure-the-pipeline">Configure the pipeline</h2>
681
681
<p>First, create a new pipeline via <ahref="http://localhost:8080/view/all/newJob">New Item</a> button in the rigth side menu of the Jenkins dashboard. The name of the pipeline could be for example <code>Animals</code> and it should be an pipeline.</p>
682
-
<p>In the configure pipeline view, scroll to the bottom and under Pipeline sub-header select <code>Pipeline script from SCM</code>. SCM type should be <code>Git</code> and Repository URL the url of this repository: <code>https://github.com/kangasta/jenkins-examples.git</code>. Ensure that branch specifier includes <code>main</code> branch of the repository and modify the Script Path to be <code>ansible-kubernetes\Jenkinsfile</code>.</p>
682
+
<p>In the configure pipeline view, scroll to the bottom and under Pipeline sub-header select <code>Pipeline script from SCM</code>. SCM type should be <code>Git</code> and Repository URL the url of this repository: <code>https://github.com/kangasta/cicd-examples.git</code>. Ensure that branch specifier includes <code>main</code> branch of the repository and modify the Script Path to be <code>docs/examples/jenkins/ansible-kubernetes/Jenkinsfile</code>.</p>
683
683
<p>After you have created the pipeline, try to execute it by clicking <em>Build Now</em>. The pipeline should have deployed the example application into the Kubernetes cluster with the default image tag (<code>cow</code>) defined in the <ahref="deploy-to-kubernetes.yml">deploy-to-kubernetes.yml</a> Ansible playbook.</p>
684
684
<p>You can find the URL of the created load-balancer from the console output of the build. Open the application with your browser or user curl to see the application response.</p>
685
685
<p>In addition, after the first execution Jenkins should have updated the project configuration to contain parameters defined in the pipeline and we can configure the image tag in <em>Build with Parameters</em> menu.</p>
@@ -705,7 +705,7 @@ <h2 id="configure-the-pipeline">Configure the pipeline</h2>
<p>The execution will likely fail with <code>ERROR: script not yet approved for use</code> message. To enable this script, navigate to <ahref="http://localhost:8080/scriptApproval/">Manage Jenkins > In-process Script Approval</a>, inspect the script, and click Approve. Then try to run the created seed project again. It should now succeed and list the created resources.</p>
660
+
<p>The execution will likely fail with <code>ERROR: script not yet approved for use</code> message. To enable this script, navigate to <ahref="http://localhost:8080/scriptApproval/">Manage Jenkins > In-process Script Approval</a>, inspect the script, and click <em>Approve</em>. Then try to run the created seed project again. It should now succeed and list the created resources.</p>
661
661
662
662
663
663
@@ -680,7 +680,7 @@ <h2 id="creating-and-running-the-seed-project">Creating and running the seed pro
Copy file name to clipboardExpand all lines: examples/jenkins/parallel-robot-pipeline/index.html
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -669,9 +669,9 @@ <h2 id="preparing-the-jenkins-instance">Preparing the Jenkins instance</h2>
669
669
<p>The pipeline provided by this example can be added to any Jenkins instance you have administrator access and can run pipeline stages with docker agent. For example, Jenkins configuration from <ahref="../dind-jenkins/">Docker-in-Docker</a> example can be used.</p>
670
670
<p>In order to be able to run the pipeline we will need <ahref="https://plugins.jenkins.io/docker-workflow/">Docker Pipeline</a> and <ahref="https://plugins.jenkins.io/robot/">Robot Framework</a> plugins. Install these plugins through <em>Available</em> tab in <ahref="http://localhost:8080/pluginManager/available">Manage Jenkins > Manage Plugins</a> and restart the Jenkins instance after these plugins have been installed. The restart can be done, for example, from the plugins page or by restarting the container with <code>docker compose down</code> and <code>docker compose up</code>.</p>
671
671
<h2id="configure-the-pipeline">Configure the pipeline</h2>
672
-
<p>First, create a new pipeline via <ahref="http://localhost:8080/view/all/newJob">New Item</a> button in the rigth side menu of the Jenkins dashboard. The name of the pipeline could be for example <code>Screenshots</code> and it should be an pipeline.</p>
673
-
<p>In the configure pipeline view, scroll to the bottom and under Pipeline sub-header select <code>Pipeline script from SCM</code>. SCM type should be <code>Git</code> and Repository URL the url of this repository: <code>https://github.com/kangasta/jenkins-examples.git</code>. Ensure that branch specifier includes <code>main</code> branch of the repository and modify the Script Path to be <code>parallel-robot-pipeline/Jenkinsfile</code>.</p>
674
-
<p>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 <code>.robot</code> 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.</p>
672
+
<p>First, create a new pipeline via <em><ahref="http://localhost:8080/view/all/newJob">New Item</a></em> button in the rigth side menu of the Jenkins dashboard. The name of the pipeline could be for example <code>Screenshots</code> and it should be an pipeline.</p>
673
+
<p>In the configure pipeline view, scroll to the bottom and under Pipeline sub-header select <code>Pipeline script from SCM</code>. SCM type should be <code>Git</code> and Repository URL the url of this repository: <code>https://github.com/kangasta/cicd-examples.git</code>. Ensure that branch specifier includes <code>main</code> branch of the repository and modify the Script Path to be <code>docs/examples/jenkins/parallel-robot-pipeline/Jenkinsfile</code>.</p>
674
+
<p>After you have created the pipeline, try to execute it by clicking <em>Build Now</em>. All Robot Framework tasks should be in Skipped state as we did not specify URL variable, see <code>.robot</code> 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.</p>
675
675
<p>Finally, If the robot log cannot be loaded after task execution, see <ahref="https://stackoverflow.com/questions/36607394/error-opening-robot-framework-log-failed">this stackoverflow post</a> for solution. To summarize, run following command in Jenkins Script Console to modify Jenkins servers Content Security Policy (CSP):</p>
0 commit comments