It would be nice to see this plugin support the CloudBees CI platform.
In a CloudBees CI setup, plugins aren't extracted to their usual location as seen in a standalone Jenkins instance. In CloudBees CI, plugins are extracted to /tmp/jenkins/plugins where in a standalone Jenkins server they're extracted to {JENKINS_HOME}/plugins.
This is problematic for a CloudBees CI instance since the plugin looks for the uipath-automation-package.jar in {JENKINS_HOME}/plugins/uipath-automation-package.
This plugin is considered a Tier 3 plugin by CloudBees and isn't part of their Plugin Assurance program.
Upstream changes
No response
Are you interested in contributing this feature?
I am but may not have the cycles depending on the level of effort here. So far, we've managed to get things working within a CloudBees CI instance by copying the extracted plugin directory to the expected location. Testing has been going well aside from some issues being sorted out with UiPath support.
With all of that said, if the only change is in the logic I've linked then that's rather straight-forward, in my opinion. However, I feel other areas may need investigation since all of our testing is conducted using a remote Windows Jenkins agent.
What feature do you want to see added?
It would be nice to see this plugin support the CloudBees CI platform.
In a CloudBees CI setup, plugins aren't extracted to their usual location as seen in a standalone Jenkins instance. In CloudBees CI, plugins are extracted to
/tmp/jenkins/pluginswhere in a standalone Jenkins server they're extracted to{JENKINS_HOME}/plugins.This is problematic for a CloudBees CI instance since the plugin looks for the
uipath-automation-package.jarin{JENKINS_HOME}/plugins/uipath-automation-package.This plugin is considered a Tier 3 plugin by CloudBees and isn't part of their Plugin Assurance program.
Upstream changes
No response
Are you interested in contributing this feature?
I am but may not have the cycles depending on the level of effort here. So far, we've managed to get things working within a CloudBees CI instance by copying the extracted plugin directory to the expected location. Testing has been going well aside from some issues being sorted out with UiPath support.
With all of that said, if the only change is in the logic I've linked then that's rather straight-forward, in my opinion. However, I feel other areas may need investigation since all of our testing is conducted using a remote Windows Jenkins agent.