Can I add a "publish" button to a build page

70 views
Skip to first unread message

Jonathan Hodgson

unread,
Jul 12, 2016, 8:57:45 AM7/12/16
to Jenkins Users
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 is seems to me would be to have a button on the build page where I could trigger a groovy script to do this. Is there a plugin which would facilitate this?

regards

Jon

Eric Pyle

unread,
Jul 12, 2016, 9:24:00 AM7/12/16
to jenkins...@googlegroups.com

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

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/22e1eeef-42a3-4604-ba1a-5731e1b91efd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Greg Smith

unread,
Jul 12, 2016, 4:57:29 PM7/12/16
to Jenkins Users
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-36089

Has anyone found any other solution for this use case (Need to take actions on a specific build) when using multibranch pipeline builds?

Cheers,
Greg

Vincent Latombe

unread,
Jul 12, 2016, 5:25:16 PM7/12/16
to Jenkins Users
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 pending builds you didn't approve after a given time.

Vincent

Michael Kobit

unread,
Jul 12, 2016, 6:15:14 PM7/12/16
to Jenkins Users

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.


Reply all
Reply to author
Forward
0 new messages