Locks and Latches plugin

Plugin Information

Plugin ID locks-and-latches
Latest Release 0.6
Latest Release Date Apr 16, 2010
Sources Subversion
Support Eclipse Hudson Forum
Issue Tracking Eclipse Bugzilla

This plugin allows you to control the parallel execution of jobs.

Locks and Latches plugin

This plugin allows you to control the parallel execution of jobs.

  • Locks are used to discourage jobs from executing in parallel.
  • Latches are used to encourage jobs to execute in parallel.

At present only Locks have been implemented.

Version History

Version 0.6.1 or 0.7 (not yet released)

  • Implemented HUDSON-8482: Additional information is displayed in builds log to know which locks are being acquired

Version 0.6 (16 Apr 2010)

  • The list of locks is now alphabetically sorted when saving the global configuration

Version 0.5 (26 Dec 2009)

  • Fix broken help link
  • Update uses of deprecated APIs

Version 0.4 (17 Oct 2008)

  • Bugfix for hanging builds

Version 0.3 (12 Oct 2008)

Version 0.2 (03 Dec 2007)

  • Initial release
  • Only implements Lock functionality

Labels:

plugin-trigger plugin-trigger Delete
plugin-buildwrapper plugin-buildwrapper Delete
tier3-hudson-plugin tier3-hudson-plugin Delete
Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.
  1. Mar 12, 2010

    Alex Lombardi says:

    Are there plans for a plug-in that will block a list of jobs from bein...

    Are there plans for a plug-in that will block a list of jobs from being build when a specific job is running, but which will not also exclude members of that list from running concurrently? The current setup of the Locks functionality necessitates a lock for each paired project and when you have hundreds of jobs this becomes a cumbersome process.

  2. Mar 16, 2010

    Peter Schuetze says:

    Does this plugin works with the m2extra steps plugin? According to the console o...

    Does this plugin works with the m2extra steps plugin? According to the console output only the main maven buildstep is protected by the locks and pre build steps as well as the post build steps are outside of the logged area. I need the pre and post steps also being protected by the locks?

  3. May 31, 2010

    Ben J Warner says:

    Agree with Alex.  Having a seperate lock for each pair of projects is not m...

    Agree with Alex.  Having a seperate lock for each pair of projects is not maintainable.  Would be great to be able to share a lock between more than two projects.

  4. Jul 21, 2010

    Dirk Möbius says:

    Or add an option to gather projects in "groups". In each group only one project ...

    Or add an option to gather projects in "groups". In each group only one project may be build at any given time.

  5. Jul 21, 2010

    Dirk Möbius says:

    Btw. I found out that you can misuse the Port Allocator Plugin for that: just as...

    Btw. I found out that you can misuse the Port Allocator Plugin for that: just assign the same tcp/ip port for two or more projects that you don't want to run at the same time. I use number ranges to group them, ie. 50000, 50001 etc.

  6. Aug 21, 2010

    Jason Swager says:

    Is there a way to specify the name of a lock via a variable or parameter?

    Is there a way to specify the name of a lock via a variable or parameter?

    1. Sep 03, 2010

      Romain Seguy says:

      Not for the moment.

      Not for the moment.