I seem to remember seeing something like before, but in my case I was
accidentally kicking off the original job AGAIN from the new job, so there
was a weird circular build queue going on. I'll see if I can dig up any
notes I made on the situation.


On Mon, Jan 13, 2014 at 2:27 PM, Sarah Renick <[email protected]>wrote:

> All changes plugin 1.3
> Ant Plugin 1.2
> Audit Trail 1.8
> Backup plugin 1.6.1
> Blame Upstream Committers 1.2
> Build Blocker Plugin 1.4.1
> Compact Columns 1.10
> conditional-buildstep 1.3.3
> Config File Provider Plugin 2.7.1
> Copy Artifact Plugin 1.28
> Credentials Plugin 1.9.4
> Dashboard View 2.9.2
> Dependency Graph Viewer Plugin 0.11
> Downstream build view 1.9
> Drop Down ViewsTabBar Plugin 1.6
> Environment Injector Plugin 1.89
> External Monitor Job Type Plugin 1.2
> Extra Columns Plugin 1.13
> Favorite 1.16
> Feature branch notifier 1.3
> FTP publisher plugin 1.2
> Green Balls 1.13
> HTML Publisher plugin 1.3
> Hudson Blame Subversion Plug-in 1.200
> Hudson Collapsing Console Sections Plugin 1.4.1
> Hudson Personal View 1.8
> Hudson Post build task 1.8
> Hudson Screenshot plugin 1.1
> Ivy Plugin 1.23.2
> Javadoc Plugin 1.1
> Jenkins Active Directory plugin 1.33
> Jenkins build timeout plugin 1.12.2
> Jenkins Claim Plugin 2.3
> Jenkins Clone Workspace SCM Plug-in 0.6
> Jenkins Continuous Integration game 1.19
> Jenkins CVS Plug-in 2.11
> Jenkins CVS Tagging Plug-in 1.7
> Jenkins disk-usage plugin 0.23
> Jenkins Doxygen Plug-in 0.14
> Jenkins Email Extension  Plugin 2.37.1
> Jenkins Exclusion Plug-in 0.9
> Jenkins Job Configuration History Plugin 2.5
> Jenkins jQuery plugin 1.7.2-1
> Jenkins jQuery UI plugin 1.0.2
> Jenkins Klocwork Plug-in 1.15
> Jenkins Mailer Plugin 1.8
> Jenkins Mercurial plugin 1.49
> Jenkins MSBuild Plugin 1.21
> JENKINS MSTest plugin 0.7
> Jenkins Multijob plugin 1.10
> Jenkins NUnit plugin 0.15
> Jenkins Parameterized Trigger plugin 2.22
> Jenkins Post-Build Script Plug-in 0.16
> Jenkins Priority Sorter Plugin 2.6
> Jenkins promoted builds plugin 2.14
> Jenkins Release Plugin 2.4.1
> Jenkins SSH Slaves plugin 1.5
> Jenkins Subversion Plug-in 1.54
> Jenkins Subversion Tagging Plugin 1.16
> Jenkins svnmerge plugin 1.2
> Jenkins Translation Assistance plugin 1.11
> Jenkins Violations plugin 0.7.11
> Job Import Plugin 1.2
> Job Revision Plugin 0.6
> Labeled Test Groups Publisher 1.2.6
> Last Failure Version Column 1.1
> Last Success Version Column 1.1
> LDAP Plugin 1.7
> Matrix Authorization Strategy Plugin 1.1
> Maven Integration plugin 2.1
> Monitoring 1.49.0
> NCover plugin 0.3
> PAM Authentication plugin 1.1
> Periodic Backup 1.3
> Plot plugin 1.5
> Progress Bar Column Plugin 1.0
> Project statistics Plugin 0.4
> Publish Over CIFS 0.3
> Publish Over FTP 1.10
> Publish Over SSH 1.11
> Purge Build Queue Plugin 1.0
> Rebuilder 1.20
> Role-based Authorization Strategy 2.1.0
> Run Condition Plugin 1.0
> Safe Restart Plugin 0.3
> SCM API Plugin 0.2
> Sectioned View Plugin 1.18
> Sidebar Link 1.6
> SSH Credentials Plugin 1.6
> Static Analysis Collector Plug-in 1.38
> Static Analysis Utilities 1.54
> SVN Publisher plugin 0.1
> Tag Cloud Plugin 1.6
> Task Scanner Plug-in 4.38
> Timestamper 1.5.8
> Token Macro Plugin 1.9
> Tracking SVN Plugin 1.1
> Version Number Plug-In 1.4.1
> View Job Filters 1.26
> Visual SourceSafe Plugin 1.9
> Warnings Plug-in 4.38
> Windows Slaves Plugin 1.0
> xUnit plugin 1.78
>
> Thanks!
>
>
> On Mon, Jan 13, 2014 at 4:11 PM, Slide <[email protected]> wrote:
>
>> Which plugins do you have an what are their versions?
>>
>>
>> On Mon, Jan 13, 2014 at 2:03 PM, Sarah Renick <[email protected]>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 [email protected].
>>>
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>
>>
>>
>> --
>> Website: http://earl-of-code.com
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Jenkins Users" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/jenkinsci-users/qZGiVCVcJKk/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to
>> [email protected].
>>
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>  --
> 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].
> For more options, visit https://groups.google.com/groups/opt_out.
>



-- 
Website: http://earl-of-code.com

-- 
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].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to