This above (input with timeout) is what we are currently doing. When the
milestone step is done (see
https://issues.jenkins-ci.org/plugins/servlet/mobile#issue/JENKINS-27039),
I believe we will switch to using that instead.
On Tue, Jul 12, 2016, 16:25 Vincent Latombe
wrote:
> You could use an in
You could use an input step (
https://jenkins.io/doc/pipeline/steps/pipeline-input-step/#code-input-code-wait-for-interactive-input)
to require manual validation.
Wrap it in a timeout
https://jenkins.io/doc/pipeline/steps/workflow-basic-steps/#code-timeout-code-enforce-time-limit
to clean-up pendin
I have exactly this same need, but with pipeline builds.
The Promotion plugin works awesome for regular builds, but unfortunately
does not work with pipeline builds.
I created this Jira to track enhancing the plugin to support pipeline
builds: https://issues.jenkins-ci.org/browse/JENKINS-3
You might take a look at the Promoted Builds plugin. It allows you to
manually "promote" a particular build, and trigger other actions. It's
designed exactly for this sort of situation.
Eric
On 7/12/2016 8:57 AM, Jonathan Hodgson wrote:
Hi,
If a build is successful (compiled correctly, pass
Hi,
If a build is successful (compiled correctly, passed all tests), I may then
want to send it out to beta testers. Which means copying the built binary
to a location where they can find it, and sending out emails. I don't want
to do this for exery successful build though.
A sensible solution
