Slave operations fail when there's a svn browser plugin installed and configured

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      When a Polarion svnwebclient plugin (perhaps other svn browser plugin as well)
      is installed, and a project which may be built on a slave server has
      svnwebclient defined as a browser, the slave build will fail, since the slave
      computer won't find the jar of the plugin.
      The expected behavior should be that only the master Hudson will use this
      plugin, and the slaves won't be dependent upon it (since the web interface is
      used only on master).

            Assignee:
            Unassigned
            Reporter:
            roman_shterenzon
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: