Jenkins user acceptance step in pipeline

I have a project and pipeline created in my jenkins instance that looks like this. enter image description here

This can be described as:

  • [Project]

    - Create a project
  • [Project Deploy Test]

    - Deploys the project to a test server
  • [Project UA Test]

    - user accept step where the user has to manually test and accept
  • [Project Deploy Prod]

    - After the user has accepted the UA test, the build is deployed for production

All steps work well except for the step [Project UA Test]

. This step should just be a button or something that the user can manually trigger when he or she is happy with the build.

The question is, How can I configure this step to force some user intervention (for example by clicking a button) before moving on to the next step?


I've tried making the assembly parameterized with a select parameter, but I'm not sure if I'm doing the right thing.

enter image description here

+3


source to share


2 answers


Promoted Builds plugin

https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin

You can use the Promoted Builds Plugin which has a manual submission workflow.

You may have:

  • [Project]

    [Project Deploy Test]

    [Project UA Test]

  • [Project UA Test]

    - (manual promotion) → [Project Deploy Prod]

Explanation: As usual, until custom acceptance tests are completed. Once complete, you can follow the manual promotion process. The advancement process can be configured to start downstream assembly; therefore, in effect, your pipeline is resuming.

Supply pipeline plugin



(note: I haven't played with this plugin, so I am just guessing)

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

The Pipeline Delivery Plugin lets you set up a job for a postbuild operation, which is a manual trigger, and allows the pipeline to resume.

Write your own?

Conceptually, to break your pipeline and the user "confirms" the build, well, the build needs to provide an action that can be taken after the build is complete. For example.

  • KeepBuildForEverAction

    (keep building forever)
  • ClaimBuildAction

    (request plugin)
+2


source


The Workflow plugin plugin supports this use case with a step input

.



+1


source







All Articles