This is due to UpDownStreamNumberSychronizedNotify not working as of 
1.5.32.1  JENKINS-21154 <https://issues.jenkins-ci.org/browse/JENKINS-21154>

On Monday, January 13, 2014 4:03:11 PM UTC-5, Sarah Renick wrote:
>
> This is my first question to the group so please bear with me.
> We upgraded from Jenkins 1.52x (can't remember exactly) to 1.546 and also 
> upgraded all our plugins.  We have 4 build jobs.  CommitBuild1 triggers 
> CommitBuild2 which triggers CommitBuild3 which triggers CommitBuild4.  All 
> were working before the upgrade.  After the upgrade the build tiggers are 
> not working.  The first job completes and the last line in the console 
> output is: 
> 15:53:48 CommitBuild2 #2703 is already in the queue
> But, the queue shows no jobs and CommitBuild2 is never run.  
> Has anyone experienced this with the lastest releases?
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to