[JENKINS-30086] Steps help and decription clean up

Originally-Committed-As: 0b1c5dcd53f0a456ef243a360ad36f6f23cc8bbe
jenkinsci · Sep 25, 2015 · eadc690 · eadc690
1 parent e3ea054
commit eadc690
Show file tree

Hide file tree

Showing 2 changed files with 13 additions and 0 deletions.
diff --git a/...in/resources/org/jenkinsci/plugins/workflow/support/steps/StageStep/help-concurrency.html b/...in/resources/org/jenkinsci/plugins/workflow/support/steps/StageStep/help-concurrency.html
@@ -0,0 +1,7 @@
+<p>
+    Concurrency level.
+</p>
+<p>
+    A concurrency of one is useful to let you lock a singleton resource, such as deployment to a single target server. 
+    Only one build will deploy at a given time: the newest which passed all previous stages
+</p>
diff --git a/support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/StageStep/help.html b/support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/StageStep/help.html
@@ -0,0 +1,6 @@
+<div>
+    By default, flow builds can run concurrently. 
+    The stage command lets you mark certain sections of a build as being constrained by limited concurrency.
+    Newer builds are always given priority when entering such a throttled stage; older builds will simply exit early if 
+    they are preëmpted.
+</div>