×
Find plugins

Exclusion0.12Minimum Jenkins requirement: 1.609.1ID: Exclusion

Installs: 1506
Last released: a year ago
Maintainers
Anthony Roux
Dependencies
No dependencies found

Plugin Information

Plugin ID

Exclusion

Changes

In Latest Release
Since Latest Release

Latest Release
Latest Release Date
Required Core
Dependencies

0.12 (archives)
Apr 19, 2016
1.609.1

Source Code
Issue Tracking
Pull Requests
Maintainer(s)

GitHub
Open Issues
Pull Requests
Anthony Roux (id: anthonyRoux)

Usage

Installations

2016-Sep 1453
2016-Oct 1385
2016-Nov 1417
2016-Dec 1388
2017-Jan 1443
2017-Feb 1439
2017-Mar 1533
2017-Apr 1491
2017-May 1587
2017-Jun 1526
2017-Jul 1490
2017-Aug 1506

This plugin manages exclusion between jobs.

About this plugin

This plugin is inspired by the Port-Allocator plugin.

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

The Exclusion plugin allows you to assign resource names to jobs on Jenkins.The plugin will ensure that jobs sharing a same resource will not be executed at the same time. The resource name is a semaphore.

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

Configuration

Firstly you have to activate the plugin by checking the box “Add resource to manage exclusion”. It allows you to add resources. A resource is 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 build steps included in a critical zone will be managed by Exclusion plugin.


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

Administration Panel

When you are on the home page of Jenkins, you can access the Administration Panel.

In this page, you can see all resources configured. The status (Action) of a job is set to "Currently Used" when the job is running (if he has a resource configured). It means that the resource is currently allocated -> the other jobs using the same resource can’t be run at this moment.

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

About me

Owner & maintainer of the project: GitHub: anthonyroux & Twitter: AnthonyRoux_

Change Log

Version 0.12 (Apr 19, 2016)

Contribution of Oleksandr Kulychok

  • Fixed Administration panel 

Version 0.11 (Oct 25, 2015)

Contribution of Emanuel Zattin

  • Add support for the Workflow plugin.

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)

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

Version 0.7 (July 7, 2012)

  • JENKINS-12250 Critical block can not be added into conditional step

Version 0.6 (Jun 19, 2011)

ArchivesGet past versions
Labels