Build Blocker Plugin: How can I tell what is blocking a job from running

[Steven Murphy]

Hello,

I am using the Build Blocker Plugin to stop conflicting jobs running at the same time.  Most of the time things work perfectly, however sometimes I get a problem where a node is blocked where it should not be (or at least I think it should not)

The information in the build queue says "Waiting for next available executor on AIX_TRUNK", however no other project is running on that node (and the other nodes in the multi-config project have been able to run).

Is there a way I can find out exactly what the plugin thinks is blocking the executor?  A file on the machine or maybe some commands to execute in the script console?

Thanks,

Steve

A bit more details on my Jenkins and plugin versions.

• Jenkins Version: 1.596

• Ant Plugin: 1.2
  
• Build Blocker Plugin: 1.4.1
  
• build-name-setter: 1.3
  
• Changes since last successfull build Plugin: 0.5
  
• Config File Provider Plugin: 2.7.5
  
• Credentials Plugin: 1.18
  
• CVS Plug-in: 2.12
  
• Email Extension Plugin: 2.39
  
• External Monitor Job Type Plugin: 1.4
  
• Javadoc Plugin: 1.3
  
• jQuery plugin: 1.7.2-1
  
• JUnit Attachments Plugin: 1.3
  
• JUnit Plugin: 1.3
  
• LDAP Plugin: 1.11
  
• Mailer Plugin: 1.12
  
• MapDB API Plugin: 1.0.6.0
  
• Matrix Authorization Strategy Plugin: 1.2
  
• Matrix Project Plugin: 1.4
  
• Maven Integration plugin: 2.8
  
• Multi slave config plugin: 1.2.0
  
• Next Build Number Plugin: .1
  
• OWASP Markup Formatter Plugin: 1.3
  
• PAM Authentication plugin: 1.2
  
• SCM API Plugin: 0.2
  
• Script Security Plugin: 1.12
  
• SSH Credentials Plugin: 1.10
  
• SSH Slaves plugin: 1.9
  
• Static Code Analysis Plug-ins: 1.65
  
• Subversion Plugin: 2.3
  
• Test Results Analyzer Plugin: 0.1.3
  
• Token Macro Plugin: 1.10
  
• Translation Assistance plugin: 1.12
  
• Wall Display Master Project: 0.6.27
  
• Windows Slaves Plugin: 1.0
  

[Matthew...@diamond.ac.uk]

>> I am using the Build Blocker Plugin to stop conflicting jobs running at the same time. ...

I can’t help with your specific question, but are you are aware of https://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin which looks like it can achieve the same things as the build blocker plugin, plus more ...

Matthew

--
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom

[Steven Murphy]

Thanks for the reply.  

I'll give a little more detail on our configuration so you can maybe advise me if that plugin will meet our needs.

Each SVN archive being monitored has 6 projects

TRUNK_TRIG_32 - Triggered by a svn commit and runs a small set of quick tests.  32bit testing.

TRUNK_TRIG_64 - Triggered by a svn commit and runs a small set of quick tests.  64bit testing

TRUNK_NIGHT_32 - Executes every night and runs an extended set of tests.  32bit testing

TRUNK_NIGHT_64 - Executes every night and runs an extended set of tests.  64bit testing

TRUNK_WE_32 - Executes each weekend and runs a super set of tests. 32bit testing

TRUNK_WE_64 - Executes each weekend and runs a super set of tests. 64bit testing

Due to limited resources all 6 projects share the same nodes.  To try make best use of the resources we allow 2 projects to execute at the same time.  However due to shared resources and such we cannot have projects of the same working mode running at the same time.  So only 1 32bit project can execute at any one time (same with the 64bit projects).

The Build Blocker Plugin configuration is like this :- 

TRUNK_TRIG_32

.*TRUNK_NIGHT_32

.*TRUNK_WE_32

TRUNK_TRIG_64

.*TRUNK_NIGHT_64

.*TRUNK_WE_64

TRUNK_NIGHT_32

.*TRUNK_TRIG_32

.*TRUNK_WE_32

TRUNK_NIGHT_64

.*TRUNK_TRIG_64

.*TRUNK_WE_64

TRUNK_WE_32

.*TRUNK_TRIG_32

.*TRUNK_NIGHT_32

TRUNK_WE_64

.*TRUNK_TRIG_64

.*TRUNK_NIGHT_64

Can I get the same functionality with the Throttle Concurrent Builds Plugin ?

Thanks,

Steve