jenkinsci / ownership-plugin

Jenkins plugin. Provides explicit ownership of jobs and agents

Ownership Plugin for Jenkins

This plugin provides an ownership engine for Jenkins automation server.

Supported features

• Ownership management for jobs, folders, runs and nodes (Summary boxes, ListView columns, etc.)
• Injection of ownership variables into the build environment
• Easy MailTo links for "Contact owners" and "Contact admins" with pre-formatted messages
• Ownership-Based Security (Role Strategy, Job Restrictions, Authorize Project, etc.)
• Integration with Jenkins Pipeline
• Ownership Filter for List Views

Documentation

• Configuration
• Ownership-Based Security
• AbstractProject Integration
• Pipeline Integration
• Contributing
• Changelog

Examples

Below you can find several Ownership Plugin UI examples.

Ownership Info Summary box:

Ownership Column:

Plugin Integrations

Ownership Plugin provides integration with multiple Jenkins plugins:

• Role Strategy - see Ownership-Based Security
• Job Restrictions - see Ownership-Based Security
• Authorize Project - see Ownership-Based Security
• Token Macro - see AbstractProject Integration
• Pipeline - see Pipeline Integration

The plugin also contributes extension points, which can be used by other plugins.

License

MIT License

Changelog

See GitHub releases for recent releases. Changelog for 0.12.1 and older versions is available here.

ownership-plugin's Issues

Exception on save Configure specific access rights

Jenkins (2.281) + Ownership Plugin (0.13) on Windows Server 2016
Role based authentication is used
Click Configure specific access rights -> Use item-specific security -> Save
The attached exception occurs:
Caught unhandled exception.txt

Caught unhandled exception with ID 6744eb32-e605-4309-ab36-94154f732cf5
java.io.IOException: Ownership is not configured for hudson.model.FreeStyleProject@630b125f[Restricted/SBHasp]
	at com.synopsys.arc.jenkins.plugins.ownership.jobs.JobOwnerHelper.setProjectSpecificSecurity(JobOwnerHelper.java:172)
	at com.synopsys.arc.jenkins.plugins.ownership.jobs.JobOwnerJobAction.doProjectSpecificSecuritySubmit(JobOwnerJobAction.java:146)
	at java.lang.invoke.MethodHandle.invokeWithArguments(Unknown Source)
	at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396)
	at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408)
	at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212)
	at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145)
	at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:536)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:766)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:898)
	at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:457)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:766)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:898)
	at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:281)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:766)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:898)
	at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:281)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:766)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:898)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:694)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:240)

Duplicate class definition for OwnershipGlobalVariableImpl

Hi,
I'm using the plugin in a Declarative Pipeline. I access the job owners in two different stages, in a normal build stage and in the cleanup stage.
Unfortunately I now sometimes get the following error:

java.lang.LinkageError: loader (instance of  org/jenkinsci/plugins/workflow/cps/CpsGroovyShell$CleanGroovyClassLoader): attempted  duplicate class definition for name: "org/jenkinsci/plugins/ownership/model/OwnershipGlobalVariableImpl"

I don't think it has something to do with it, but the problem appeared only (?) after introducing the feature of sequential stages. However, the ownership plugin is only accessed within one of the two stages blocks.

Below you find the functions that I'm using in a custom step of my shared library. This code is accessed two times, in the normal stage and in the cleanup stage:

• ownership.job.ownershipEnabled
• ownership.job.primaryOwnerEmail
• ownership.job.secondaryOwnerEmails

I'm using version 0.12.1 of the plugin.