Exclusion-Plugin

Skip to end of metadata
Go to start of metadata

Plugin Information

Plugin ID Exclusion Changes In Latest Release
Since Latest Release
Latest Release
Latest Release Date
Required Core
Dependencies
0.10 (archives)
Jan 25, 2014
1.489
Source Code
Issue Tracking
Pull Requests
Maintainer(s)
GitHub
Open Issues
Pull Requests
Anthony Roux (id: anthonyRoux)
Usage Installations 2014-May 711
2014-Jun 715
2014-Jul 778
2014-Aug 776
2014-Sep 825
2014-Oct 858
2014-Nov 853
2014-Dec 864
2015-Jan 919
2015-Feb 940
2015-Mar 998
2015-Apr 1025

This plugin manages exclusion between jobs.

About this plugin

This plugin is inspired by Port-Allocator plugin.

The purpose of this plugin is to manage conflicts betweens jobs.

Exclusion plugin allows you to assign resources name to every job on Jenkins. This feature will be in charge of not building jobs that have same resources at the same time. Exclusion plugin is based on a semaphore system.

With the second part of the plugin you can, in an administration panel, see all resources currently configured in each job. You can also see when a resource is allocated and, thanks to the release button, you can release a resource currently in use.

Configuration

First of all you have to activate the plugin by clicking on “Add resource to manage exclusion”. That allows you to add resources. Resources are represented by a name (String). You can add as much resources as needed.

Secondly you have to determine the critical zone, delimited by a start (Critical Block Start) and an end (Critical Block End). All builds steps that we can found in critical zone will be managed by Exclusion plugin.


If you don’t add a start block the plugin won’t be used. If you don’t add an end block, resources will be release after the last build step.

Administration Panel

When you are on Jenkins home page you can go to the Administration Panel.

Here you can see all resources currently configured in each job. When a job is running and it’s using a resource you can see in Action “Currently Used”, it means that the resource is currently allocated, so the others jobs that have resource which have the same name can’t be run at this moment.

You can release a resource by selecting resource name in the combo box (that show only resources that are used) and clicking on “Release resource button”.

Change Log

Version 0.10 (Jan 25, 2014)

Version 0.9 (Nov 18, 2013)

  • Fixed a security vulnerability that allows non-administrator users from releasing resources that are currently held (SECURITY-53)

Version 0.8 (Nov 8, 2012)

  • issue #14953 Exclusion plugin sometimes reports a resource as locked when it is not. Jobs hang as a result.

Version 0.7 (July 7, 2012)

  • issue #12250 Critical block can not be added into conditional step

Version 0.6 (Jun 19, 2011)

Labels

Edit
plugin-builder plugin-builder Delete
exclusion exclusion Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Add Comment