[JIRA] (JENKINS-58195) Artifactory plugin does not support having multiple instances of the build wrapper in Web UI

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev updated an issue

Jenkins / JENKINS-58195 Artifactory plugin does not support having multiple instances of the build wrapper in Web UI Change By: Oleg Nenashev Summary: promoted builds plugin incompatible with Artifactory plugin does not support having multiple instances of the build wrapper in Web UI Add Comment

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

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev assigned an issue to Eyal Ben Moshe

Jenkins / JENKINS-58195 Artifactory plugin does not support having multiple instances of the build wrapper in Web UI

Change By: Oleg Nenashev Assignee: Oleg Nenashev Eyal Ben Moshe

Add Comment

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev commented on JENKINS-58195

Re: Artifactory plugin does not support having multiple instances of the build wrapper in Web UI Related issue on the JFrog's side: https://github.com/jfrog/jenkins-artifactory-plugin/issues/166

Add Comment

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev edited a comment on JENKINS-58195

Re: Artifactory plugin does not support having multiple instances of the build wrapper in Web UI

> I had a look at the artifactory plugin code. It seems the plugin assumes that all UI elements can only exist once in the DOM. Found lots of getElementById calls which would explain why everything looks messed up. Thanks for the investigation [~schlebu]! Wr W . r. t. the Artifactory plugin, this is not how Jenkins plugins should be designed. Not the first case for the Artifactory plugin, actually. It is not a responsibility of this plugin to fix bogus assumptions in other plugins. I will assign the issue to the Artifactory plugin maintainers so that can take a look. Although I have some ideas how to fix that, unfortunately I cannot contribute to the Artifactory plugin due to its Contributor License Agreement restrictions. Whomever is am Artifactory pluin plugin user, please feel free to bring up this issue with jFrog support.  For Promoted Builds users, it should be less of a problem once the plugin supports Pipeline

Add Comment