From 9d7b8f448d114bc041050c66da10dbf9826b28a1 Mon Sep 17 00:00:00 2001 From: Marcin Grzejszczak Date: Fri, 24 Mar 2017 17:17:32 +0100 Subject: [PATCH] Updated docs --- README.adoc | 11 ++++++++++- docs/JENKINS.adoc | 11 ++++++++++- docs/spring-cloud-pipelines.html | 31 ++++++++++++++++++++++++++++++- jenkins/README.adoc | 11 ++++++++++- 4 files changed, 60 insertions(+), 4 deletions(-) diff --git a/README.adoc b/README.adoc index 5f64ea16..0ceb2707 100644 --- a/README.adoc +++ b/README.adoc @@ -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 diff --git a/docs/JENKINS.adoc b/docs/JENKINS.adoc index 8820c6fa..4ce6e101 100644 --- a/docs/JENKINS.adoc +++ b/docs/JENKINS.adoc @@ -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 diff --git a/docs/spring-cloud-pipelines.html b/docs/spring-cloud-pipelines.html index 0f7ab9d3..95eaa90b 100644 --- a/docs/spring-cloud-pipelines.html +++ b/docs/spring-cloud-pipelines.html @@ -2441,7 +2441,7 @@

Declarative pipeline & Blue Ocean<
-blue 6 +blue 7
Step 7: The pipeline is done!
@@ -2449,6 +2449,35 @@

Declarative pipeline & Blue Ocean<

   

+
+ + + + + +
+
Important
+
+There is no possibility of restarting pipeline from specific stage, after failure. Please +check out this 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 issue for +and this StackOverflow question +for more information. +
+

Optional steps

diff --git a/jenkins/README.adoc b/jenkins/README.adoc index 1b6a2603..dcdd5f17 100644 --- a/jenkins/README.adoc +++ b/jenkins/README.adoc @@ -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