Skip to content
This repository has been archived by the owner on Apr 20, 2022. It is now read-only.

Commit

Permalink
Updated docs
Browse files Browse the repository at this point in the history
  • Loading branch information
@marcingrzejszczak
marcingrzejszczak committed Mar 24, 2017
1 parent 6ba1e85 commit 9d7b8f4
Show file tree
Hide file tree
Showing 4 changed files with 60 additions and 4 deletions.
11 changes: 10 additions & 1 deletion README.adoc
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1020,12 +1020,21 @@ image::{jenkins-root-docs}/blue_6.png[caption="Step 6: ", title="The build is in
{nbsp}
{nbsp}

image::{jenkins-root-docs}/blue_6.png[caption="Step 7: ", title="The pipeline is done!"]
image::{jenkins-root-docs}/blue_7.png[caption="Step 7: ", title="The pipeline is done!"]

{nbsp}
{nbsp}


IMPORTANT: There is no possibility of restarting pipeline from specific stage, after failure. Please
check out this https://issues.jenkins-ci.org/browse/JENKINS-33846[issue] for more information

WARNING: Currently there is no way to introduce manual steps in a performant way. Jenkins is
blocking an executor when manual step is required. That means that you'll run out of executors
pretty fast. You can check out this https://issues.jenkins-ci.org/browse/JENKINS-36235[issue] for
and this http://stackoverflow.com/questions/42561241/how-to-wait-for-user-input-in-a-declarative-pipeline-without-blocking-a-heavywei[StackOverflow question]
for more information.

=== Optional steps

[[jenkins_optional]] All the steps below are not necessary to run the demo. They are needed only
Expand Down
11 changes: 10 additions & 1 deletion docs/JENKINS.adoc
View file
Original file line number Diff line number Diff line change
Expand Up @@ -290,12 +290,21 @@ image::{jenkins-root-docs}/blue_6.png[caption="Step 6: ", title="The build is in
{nbsp}
{nbsp}

image::{jenkins-root-docs}/blue_6.png[caption="Step 7: ", title="The pipeline is done!"]
image::{jenkins-root-docs}/blue_7.png[caption="Step 7: ", title="The pipeline is done!"]

{nbsp}
{nbsp}


IMPORTANT: There is no possibility of restarting pipeline from specific stage, after failure. Please
check out this https://issues.jenkins-ci.org/browse/JENKINS-33846[issue] for more information

WARNING: Currently there is no way to introduce manual steps in a performant way. Jenkins is
blocking an executor when manual step is required. That means that you'll run out of executors
pretty fast. You can check out this https://issues.jenkins-ci.org/browse/JENKINS-36235[issue] for
and this http://stackoverflow.com/questions/42561241/how-to-wait-for-user-input-in-a-declarative-pipeline-without-blocking-a-heavywei[StackOverflow question]
for more information.

=== Optional steps

[[jenkins_optional]] All the steps below are not necessary to run the demo. They are needed only
Expand Down
31 changes: 30 additions & 1 deletion docs/spring-cloud-pipelines.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2441,14 +2441,43 @@ <h3 id="_declarative_pipeline_blue_ocean">Declarative pipeline &amp; Blue Ocean<
</div>
<div class="imageblock">
<div class="content">
<img src="img/jenkins/blue_6.png" alt="blue 6">
<img src="img/jenkins/blue_7.png" alt="blue 7">
</div>
<div class="title">Step 7: The pipeline is done!</div>
</div>
<div class="paragraph">
<p>&#160;
&#160;</p>
</div>
<div class="admonitionblock important">
<table>
<tr>
<td class="icon">
<div class="title">Important</div>
</td>
<td class="content">
There is no possibility of restarting pipeline from specific stage, after failure. Please
check out this <a href="https://issues.jenkins-ci.org/browse/JENKINS-33846">issue</a> for more information
</td>
</tr>
</table>
</div>
<div class="admonitionblock warning">
<table>
<tr>
<td class="icon">
<div class="title">Warning</div>
</td>
<td class="content">
Currently there is no way to introduce manual steps in a performant way. Jenkins is
blocking an executor when manual step is required. That means that you&#8217;ll run out of executors
pretty fast. You can check out this <a href="https://issues.jenkins-ci.org/browse/JENKINS-36235">issue</a> for
and this <a href="http://stackoverflow.com/questions/42561241/how-to-wait-for-user-input-in-a-declarative-pipeline-without-blocking-a-heavywei">StackOverflow question</a>
for more information.
</td>
</tr>
</table>
</div>
</div>
<div class="sect2">
<h3 id="_optional_steps">Optional steps</h3>
Expand Down
11 changes: 10 additions & 1 deletion jenkins/README.adoc
View file
Original file line number Diff line number Diff line change
Expand Up @@ -294,12 +294,21 @@ image::{jenkins-root-docs}/blue_6.png[caption="Step 6: ", title="The build is in
{nbsp}
{nbsp}

image::{jenkins-root-docs}/blue_6.png[caption="Step 7: ", title="The pipeline is done!"]
image::{jenkins-root-docs}/blue_7.png[caption="Step 7: ", title="The pipeline is done!"]

{nbsp}
{nbsp}


IMPORTANT: There is no possibility of restarting pipeline from specific stage, after failure. Please
check out this https://issues.jenkins-ci.org/browse/JENKINS-33846[issue] for more information

WARNING: Currently there is no way to introduce manual steps in a performant way. Jenkins is
blocking an executor when manual step is required. That means that you'll run out of executors
pretty fast. You can check out this https://issues.jenkins-ci.org/browse/JENKINS-36235[issue] for
and this http://stackoverflow.com/questions/42561241/how-to-wait-for-user-input-in-a-declarative-pipeline-without-blocking-a-heavywei[StackOverflow question]
for more information.

=== Optional steps

[[jenkins_optional]] All the steps below are not necessary to run the demo. They are needed only
Expand Down

0 comments on commit 9d7b8f4

Please sign in to comment.