Jenkins-workflow - advancement phase (better solution than enter)?

Question

We started using jenkins-workflow to manage the continuous delivery pipeline.

Here is a simple Pipeline example of what we do:

[Build project] => [Run unit tests] => [Perform integration tests] => [QA Promotion] => [Deploy in QA] => [UAT Promotion] => [Deploy in UAT]

Where: [QA Promotion] and [UAT Promotion] are the stages that expect someone to “advance” the assembly (implemented with an input step).

This is purely aesthetically pleasing, but one thing that we found not very pleasant was that each assembly that was awaiting the progress stage was displayed as “in progress” (with an indicator of progress for an indefinite time). This is strange because if the last 10 assemblies have not been deployed to QA, we end up with 10 lines of output as “working”.

I know that waiting for input will not cause a performance problem. Because if these input steps are not encapsulated inside the node, then they only consume the flyers (an unused slot, which is supposed to not take any significant processing power, src: https://github.com/jenkinsci/pipeline-plugin/ blob / master / TUTORIAL.md ).

, , , "" , .

Answer 1

10 QA, 10 ""

concurrency stage . , , , input, milestone .

Answer 2

: https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Milestone+Step+Plugin

:

Pipeline . , , ( ), .

, , , , , , , .

:

Builds pass milestones in order (taking the build number as sorter field).
Older builds will not proceed (they are aborted) if a newer one already passed the milestone.
When a build passes a milestone, any older build that passed the previous milestone but not this one is aborted (see TIP 2 below).

, , , "".

Answer 3

,

timeout(time:1, unit:'DAYS') {
    input message:'Approve deployment?'
}