[JIRA] (JENKINS-57902) Multiple upstream job triggers for downstream job triggers only old build instead of triggering latest build

4 views
Skip to first unread message

narendra.narendra2u@gmail.com (JIRA)

unread,
Jun 7, 2019, 12:47:03 AM6/7/19
to jenkinsc...@googlegroups.com
ratna polepalli created an issue
 
Jenkins / Bug JENKINS-57902
Multiple upstream job triggers for downstream job triggers only old build instead of triggering latest build
Issue Type: Bug Bug
Assignee: Unassigned
Attachments: not_latest_build.png
Components: other
Created: 2019-06-07 04:46
Priority: Critical Critical
Reporter: ratna polepalli

We have a job which builds the image. --> BUILD_JOB

We have another job that will trigger based on the build job, if it is successful then this job will trigger --> TEST_EXECUTION_JOB.

 

Now in TEST_EXECUTION_JOB --> A build runs and in execution.

Now in Queue there are 2 builds --> B and C.

 

After A builds Completes , It should pick the latest build C , but Jenkins is picking the build B(which is OLD compared to Build C).

 

I hope I explained correctly.

 

Attached the screenshot which facing issue in my jenkins job

In attached screenshot 2 builds came (i.e 858 and 859) 858 is old and 859 is latest. But my jenkins job is taking 858 to run instead of taking 859.

 

Please provide the solution that something jenkins team to work or I need to modify something in my groovy code.

 

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

slide.o.mix@gmail.com (JIRA)

unread,
Jul 17, 2019, 9:23:01 AM7/17/19
to jenkinsc...@googlegroups.com
Alex Earl commented on Bug JENKINS-57902
 
Re: Multiple upstream job triggers for downstream job triggers only old build instead of triggering latest build

If you are using Cloudbees Enterprise, I recommend contacting them for support.

Reply all
Reply to author
Forward
0 new messages