[JIRA] (JENKINS-58302) variant plugin activates extensions that should not be active

3 views
Skip to first unread message

jnord@cloudbees.com (JIRA)

unread,
Jul 2, 2019, 11:28:03 AM7/2/19
to jenkinsc...@googlegroups.com
James Nord created an issue
 
Jenkins / Bug JENKINS-58302
variant plugin activates extensions that should not be active
Issue Type: Bug Bug
Assignee: Kohsuke Kawaguchi
Components: variant-plugin
Created: 2019-07-02 15:27
Priority: Major Major
Reporter: James Nord

I create an extension that was annotated with the variants @OptionalExtension marker with required-plugins="something-not-installed"

When running the plugin in Jenkins without the required plugin I expected my Extension not to be present, but it was present and active (as shown by ExtensionList.lookup

It seems as though the requirement is not checked before creating the extension which is contrary to the documentation.

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

jnord@cloudbees.com (JIRA)

unread,
Jul 2, 2019, 11:29:03 AM7/2/19
to jenkinsc...@googlegroups.com
James Nord updated an issue
Change By: James Nord
I created an extension that was annotated with the variants {{@OptionalExtension}} marker with {{required-plugins="something-not-installed}}"


When running the plugin in Jenkins without the required plugin I expected my Extension not to be present, but it was present and active (as shown by {{ExtensionList.lookup}}

It seems as though the requirement is not checked before creating the extension which is contrary to the documentation.

 

NB, looked at this quickly with [~danielbeck] and we could not see anything wrong . in the plugin I was writing

jnord@cloudbees.com (JIRA)

unread,
Jul 2, 2019, 11:29:03 AM7/2/19
to jenkinsc...@googlegroups.com
James Nord updated an issue
I create created an extension that was annotated with the variants {{@OptionalExtension}} marker with {{required-plugins="something-not-installed}}"


When running the plugin in Jenkins without the required plugin I expected my Extension not to be present, but it was present and active (as shown by {{ExtensionList.lookup}}

It seems as though the requirement is not checked before creating the extension which is contrary to the documentation.

 

NB, looked at this quickly with [~danielbeck] and we could not see anything wrong.
Reply all
Reply to author
Forward
0 new messages