As a platform developer/cartridge user
I want to be able to load XML based cartridges on remote Jenkins slaves
So that I can disable the Jenkins master executor.
Scenario: Test loading XML based cartridge on a Jenkins master executor.
Scenario: Test loading XML cartridge on a Jenkins remote slave.
Scenario: Test loading a cartridge without XML based jobs on a master
Scenario: Test loading a cartridge without XML based jobs on a remote slave
This change uses the VirtualChannel from the Jenkins remoting interface exposed by the Jenkins build object to enable the builds workspace to be accessed independent of the location e.g. on a Jenkins slave or master. System Groovy executes on the master and therefore when running a cartridge on a slave the underlying file system is different.
This PR does not update the rest of load cartridge job to support remote slaves.
nickdgriffin
commented
7 years ago
As a platform developer/cartridge user I want to be able to load XML based cartridges on remote Jenkins slaves So that I can disable the Jenkins master executor.
Scenario: Test loading XML based cartridge on a Jenkins master executor. Scenario: Test loading XML cartridge on a Jenkins remote slave. Scenario: Test loading a cartridge without XML based jobs on a master Scenario: Test loading a cartridge without XML based jobs on a remote slave
This change uses the VirtualChannel from the Jenkins remoting interface exposed by the Jenkins build object to enable the builds workspace to be accessed independent of the location e.g. on a Jenkins slave or master. System Groovy executes on the master and therefore when running a cartridge on a slave the underlying file system is different.
This PR does not update the rest of load cartridge job to support remote slaves.
Signed-off-by: Northard, Robert A robert.a.northard@accenture.com