• Type: Bug
• Resolution: Fixed
• Priority: Major
• Component/s: parameterized-trigger-plugin
• Labels:

  None
• Environment:

  parameterized-trigger-plugin version 2.11
  Jenkins ver. 1.436

1. 

   Screen shot 2011-10-29 at 3.10.43 PM.png

   17 kB

   2011-10-29 20:19

[JENKINS-11556] Project list is not updated between builds

Jessica Austin created issue - 2011-10-29 19:57

Jessica Austin made changes - 2011-10-29 19:57

Assignee	Original: Fred G [ fredg ]	New: Jessica Austin [ livermouse ]
Description	Original: *Steps to reproduce:* Set up one blocking trigger builder config in one trigger buildstep that triggers three projects ("project1, project2, project3"). *Expected console log output should be:* {code} Started by user SYSTEM Waiting for the completion of project1 project1 #1 completed. Result was SUCCESS Waiting for the completion of project2 project2 #1 completed. Result was SUCCESS Waiting for the completion of project3 project3 #1 completed. Result was SUCCESS Finished: SUCCESS {code} *Actual output:* {code} Started by user SYSTEM Waiting for the completion of project1 project1 #1 completed. Result was SUCCESS Waiting for the completion of project1 project2 #1 completed. Result was SUCCESS Waiting for the completion of project1 project3 #1 completed. Result was SUCCESS Finished: SUCCESS {code} It might be better to show all the projects that are not yet completed, instead of just the next one. *Example:* {code} Started by user SYSTEM Waiting for the completion of project1, project2, project3 project1 #1 completed. Result was SUCCESS Waiting for the completion of project2, project3 project2 #1 completed. Result was SUCCESS Waiting for the completion of project3 project3 #1 completed. Result was SUCCESS Finished: SUCCESS {code}
Environment	Original: parameterized-trigger-plugin version 2.10	New: parameterized-trigger-plugin version 2.11
Priority	Original: Minor [ 4 ]	New: Major [ 3 ]

Jessica Austin made changes - 2011-10-29 20:19

Attachment		New: Screen shot 2011-10-29 at 3.10.43 PM.png [ 20983 ]
Description		New: h3. Steps to reproduce * Create a job and add a new "Trigger/call builds on other projects" step * For the "Projects to build" parameter, give a project name that is parameterized * Run the job once with one set of parameters --> correct project is executed * Run the job again with another set of parameters --> same project as before is executed, instead of the new one h3. For example * I have jobs with names of the form {{$\{SELECTED_PROJECT\}\-war\-$\{CODE_VERSION\}}}, e.g. datatool-war-trunk, chat-war-qa, etc * I create another job with {{SELECTED_PROJECT}} and {{CODE_VERSION}} as parameters * Within this job, I add a parameterized trigger step with {{$\{SELECTED_PROJECT\}\-war\-$\{CODE_VERSION\}}} as the project name * I run the build once with {{SELECTED_PROJECT=datatool,CODE_VERSION=trunk}} ** datatool-war-trunk is executed as expected * I run the build again with {{SELECTED_PROJECT=chat,CODE_VERSION=qa}} ** datatool-war-trunk is triggered--NOT chat-war-qa as expected h3. Possible fix I'm able to fix this by removing the "caching" for projectList within BuildTriggerConfig.java: see [here|https://github.com/jenkinsci/parameterized-trigger-plugin/blob/master/src/main/java/hudson/plugins/parameterizedtrigger/BuildTriggerConfig.java#L90]
Environment	Original: parameterized-trigger-plugin version 2.11	New: parameterized-trigger-plugin version 2.11 Jenkins ver. 1.436

Jessica Austin made changes - 2011-10-29 20:20

Assignee

Original: Jessica Austin [ livermouse ]

cjo9900 made changes - 2012-07-29 17:32

Assignee

New: cjo9900 [ cjo9900 ]

cjo9900 made changes - 2012-08-01 11:31

Resolution		New: Fixed [ 1 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

R. Tyler Croy made changes - 2016-07-25 23:54

Workflow

Original: JNJira [ 141783 ]

New: JNJira + In-Review [ 189818 ]