Repository navigation
[JENKINS-702] Slave operations fail when there's a svn browser plugin installed and configured #854
Description
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).
Originally reported by roman_shterenzon, imported from: Slave operations fail when there's a svn browser plugin installed and configured
- status: Closed
- priority: Major
- component(s): remoting
- resolution: Fixed
- resolved: 2007-08-11T13:04:03+00:00
- votes: 0
- watchers: 0
- imported: 2025-11-25
Raw content of original issue
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).
- environment:
Platform: All, OS: All
Activity
jenkins-infra-bot commentedon Aug 11, 2007
Raw content of original comment:
Fixed in 1.129.