[JIRA] (JENKINS-28735) Supporting Jobs triggered by plug-ins, API and scripts, timer

2 views
Skip to first unread message

brunodepaulak@yahoo.com.br (JIRA)

unread,
Mar 11, 2017, 8:00:02 PM3/11/17
to jenkinsc...@googlegroups.com
Bruno P. Kinoshita updated an issue
 
Jenkins / Improvement JENKINS-28735
Supporting Jobs triggered by plug-ins, API and scripts, timer
Change By: Bruno P. Kinoshita
Summary: Supporting Jobs triggered by plug-ins, API and scripts , timer
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

brunodepaulak@yahoo.com.br (JIRA)

unread,
Mar 11, 2017, 8:05:06 PM3/11/17
to jenkinsc...@googlegroups.com
Bruno P. Kinoshita reopened an issue
Change By: Bruno P. Kinoshita
Resolution: Duplicate
Status: Resolved Reopened

brunodepaulak@yahoo.com.br (JIRA)

unread,
Mar 11, 2017, 8:05:06 PM3/11/17
to jenkinsc...@googlegroups.com
Bruno P. Kinoshita resolved as Duplicate
 

Closing as duplicated, and linking to JENKINS-34618. Will maintain the work log there, but will use the attachments and description provided here (big thank you for that!). Feel free to subscribe to JENKINS-34618 to receive updates on that. Thanks!
Change By: Bruno P. Kinoshita
Status: Open Resolved
Resolution: Duplicate

brunodepaulak@yahoo.com.br (JIRA)

unread,
Mar 11, 2017, 8:05:08 PM3/11/17
to jenkinsc...@googlegroups.com
Bruno P. Kinoshita updated an issue
Change By: Bruno P. Kinoshita
Comment:
Closing as duplicated, and linking to JENKINS-34618. Will maintain the work log there, but will use the attachments and description provided here (big thank you for that!). Feel free to subscribe to JENKINS-34618 to receive updates on that. Thanks!

simontom@volny.cz (JIRA)

unread,
Jul 27, 2018, 4:26:02 AM7/27/18
to jenkinsc...@googlegroups.com
Simon Tomek commented on Improvement JENKINS-28735
 
Re: Supporting Jobs triggered by plug-ins, API and scripts, timer

Hi there, it's been another year.

Is there any update?

Or is there any workaround for how to get these dynamic params calculated even by using Timer or BuildTrigger?

Thanks
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

simontom@volny.cz (JIRA)

unread,
Jul 27, 2018, 6:20:02 AM7/27/18
to jenkinsc...@googlegroups.com
Simon Tomek edited a comment on Improvement JENKINS-28735
Hi there, it's been another year.

Is there any update?

Or is there any workaround for how to get these dynamic params calculated even by using Timer or BuildTrigger?

Thanks


 

*UPDATE*

Well, I managed to solve the problem, at least for my UseCase.

I just needed to have one master job which triggers children. Master has Choice Parameter with a list of values (e.g. 12.0, 12.xx, master). Children jobs uses specified branch from GIT. Problem is each repo uses another release branch name prefix. So, I looked for a way how to pass a version and add the specific branch name dynamically at child job.

First, I tried by using Active Choices. It worked. But only if I used the GUI. Othervise, whenever I tried to start the child job from master job and passing the version I want, it failed, because it wasn't able to recalculate the Reactive Choice value.

But then I came across _Prepare an environment for the run_. I use simple Groovy script which creates the value dynamically (adds some specific prefix to the name of GIT branch) and works like a charm..like I said before +at least for my UseCase+.

 

 

Tizkiko@gmail.com (JIRA)

unread,
Mar 18, 2019, 6:29:02 AM3/18/19
to jenkinsc...@googlegroups.com
Tizki KO commented on Improvement JENKINS-28735

I encountered in the same issue. My workaround for this is to return the first element as a list of the default selected values. so in case your script returns:

{{}}

['ONE:selected','TWO:selected','TREE:selected','FOUR:selected']

{{}}

}}{{instead, it would return:

[ONE,TWO,TREE,FOUR, ONE:selected, TWO:selected, TREE:selected, FOUR:selected]

see https://stackoverflow.com/a/55219124/947784 for more details.

{{}}
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

Tizkiko@gmail.com (JIRA)

unread,
Mar 18, 2019, 6:30:03 AM3/18/19
to jenkinsc...@googlegroups.com
Tizki KO edited a comment on Improvement JENKINS-28735
I encountered in the same issue. My workaround for this is to return the first element as a list of the default selected values. so in case your script returns:
{
{}}
{ code:java}
['ONE:selected','TWO:selected','TREE:selected','FOUR:selected'] {code}
{{ }}

{{}}{{ instead}}{{, it would return:}}
{code:java}
[ONE,TWO,TREE,FOUR, ONE:selected, TWO:selected, TREE:selected, FOUR:selected] {code}


{{}}

batek.nowak@yahoo.pl (JIRA)

unread,
May 31, 2019, 7:51:05 AM5/31/19
to jenkinsc...@googlegroups.com

I don't know if I'm good understand problem, but I found one task that i think is somehow related to this one.

https://issues.jenkins-ci.org/browse/JENKINS-42723

Please correct me if I'm wrong 
Reply all
Reply to author
Forward
0 new messages