Hi,
I’m seeing a breaking change in behavior between 10.0 and 10.1 in the way GlobalJobPreload commands are handled. The specific versions are 10.0.28.2 and 10.1.2.2. The same job runs fine using the 10.0.28.2 slave, but ends up failing when run using the 10.1.2.2 worker as the command line returned by the GlobalJobPreload is split in a way that it didn’t used to be.
An example command line looks like
Arguments: ‘/a/path/test.command --option1 ‘optionvalue-1.0’ --option2 ‘/a/nother/path foo-1.1.0 – cd /tmp; cp /bar.tgz .; tar -vxzf bar.tgz’’
In 10.0, test.command is passed the list of arguments as follows
[’–option1’, ‘optionvalue-1.0’, ‘–option2’, ‘/a/nother/path foo-1.1.0 – cd /tmp; cp /bar.tgz .; tar -vxzf bar.tgz’’]
In 10.1, test.command is passed this list of arguments
[’–option1’, “‘optionvalue-1.0’”, ‘–option2’, “’/a/nother/path”, ‘foo-1.1.0’, ‘–’, ‘cd’, ‘/tmp;’, ‘cp’, ‘/bar.tgz’, ‘.;’, ‘tar’, ‘-vxzf’, ‘bar.tgz’"]
10.1 seems to be splitting the values inside the quoted strings in the argument list. Was this an intended change? Is there a better way to structure our command lines?
Thanks in advance for the help.