Hmm, I was wondering that myself, but the pipeline job can run and populate the parameter list at runtime, so I was wondering if/hoping the multibranch can do the same
On Monday, 19 February 2018 15:14:17 UTC+11, ok999 wrote: > > I dont have much experience with multi branch job types. Nonetheless, The > below requirement may not be possible unless there is some plugin to do so. > > The job / local workspace will not have any idea of remote branches before > you trigger it. A workaround may be to start the job, create a stage that > checks out the remote branches, and use the input dsl for a users input. > > > > > > > > On Mon, Feb 19, 2018 at 9:33 AM <[email protected] <javascript:>> > wrote: > >> Correct. If I choose to "Build with parameters" I want a Branch parameter >> to list all the branches of that jobs repository, but defined in a >> Jenkinsfile as a multibranch pipeline >> >> >> On Monday, 19 February 2018 14:39:07 UTC+11, ok999 wrote: >> >>> Not sure, if i am following this requirement. Am I understanding it >>> right, if you want to list the remote branches of a repository on jenkins >>> job as a parameters? >>> >>> On Mon, Feb 19, 2018 at 8:43 AM <[email protected]> wrote: >>> >> What I want to be able to do - >>>> >>>> Have a Jenkinsfile that will automatically build a git master branch if >>>> triggered automatically on commit but prompt the user to select from a >>>> branch if run manually >>>> >>>> Selecting the master if triggered automatically is no problem using >>>> parameter default value, but I cannot for the life of me figure out a way >>>> to populate the branch parameter >>>> >>>> I've looked for a way to use the Git parameters plugin but while there >>>> is plenty of examples on how to use it though the gui with a pipeline >>>> script, I cant find any documentation or examples on how to use it with >>>> multibranch/Jenkinsfile using code >>>> >>>> can anyone help with the above, or any other method? >>>> >>>> thanks >>>> >>>> -- >>>> 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 [email protected]. >>> >>> >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-users/1995eb74-988c-4fb2-b972-f849771769c2%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/jenkinsci-users/1995eb74-988c-4fb2-b972-f849771769c2%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- >>> Sent from mobile device, excuse typos if any. >>> >> -- >> 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 [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/c987a2f1-9e25-4b20-bfa1-233a47a0ea43%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-users/c987a2f1-9e25-4b20-bfa1-233a47a0ea43%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- > Sent from mobile device, excuse typos if any. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d4462e32-4ff0-489c-adb7-3fce522e22d9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
