How to trigger a pipeline, passing in custom parameters via a UI

[Pat Podenski]

This question relates to a handy feature that is present in Jenkins - wondering if this can be done with ThoughtWorks Go?

I want to manually trigger a pipeline passing in a custom parameter - this is different than the trigger that allows one to select a revision. Jenkins has a customizable UI page in which I can define custom parameters (typed and with default values plus description) and then when running the build, user is prompted to enter the parameter values prior to running the build.

While this feature is not essential, it is really quite useful in Jenkins.

Any ideas on whether this can be done and how would be appreciated.

[Ketan Padegaonkar]

Go has the ability commonly known as "trigger with options" that may be similar to what you're looking for. If you have a pipeline with one or more dependencies and environment variables. Go will let you tweak the dependencies and environment variables before triggering the run.

I've attached some screenshot if it helps.

- Ketan

--
You received this message because you are subscribed to the Google Groups "go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email to go-cd+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Aravind SV]

Yes, that's right. To get to that dialog box, you need to click the button highlighted in blue in the screenshot below.

Cheers,

Aravind

[Pat Podenski]

Ketan,

Thanks, that's what I was looking for. Is there a way to disable the NON-parameterized UI button so that the user must select the one on the right?

I suppose if it is not possible to disable the NON-parameterized UI button, the job could fail and the error message could instruct to use the parameterized UI button instead. In Jenkins this UI issue is handled by only exposing a parameterized UI trigger item.

[Aravind SV]

Hey Pat,

On Tue, Apr 8, 2014 at 4:47 PM, Pat Podenski <pat.po...@gmail.com> wrote:

Thanks, that's what I was looking for. Is there a way to disable the NON-parameterized UI button so that the user must select the one on the right?

No, there is no way currently.

I suppose if it is not possible to disable the NON-parameterized UI button, the job could fail and the error message could instruct to use the parameterized UI button instead. In Jenkins this UI issue is handled by only exposing a parameterized UI trigger item.

Yes, we know that some users have set an environment variable that needs to be changed with the parameterized ("Trigger With Options") UI and the first task ensures that the environment variable is set.

Cheers,

Aravind

[fabricio duarte]

Would it be possible to have the trigger with options UI button to include parameters ?

I'm trying to specify the job resources dynamically, so that it uses a default value but would allow to change/extend the job resource filters using the trigger with options button.

It seems that resources are able to leverage pipeline parameters, but those would require changing the pipeline definition each time...

Thanks,

--

Fabricio