So well I tried renaming the job removing the spaces (after I noticed that the other jobs didn't have names in) and now it works fine. The script is running in the "Execute shell" block yes. But the thing is that the error comes before my script is executed, when Jenkins is still trying to set up the directories to run the job, so I'm a bit surprised because it looks like at this point it should handle the spaces.
I'm not using any Jenkins variable in my script if that makes a difference.. Anyway it's fine now so problem solved, thanks On Tuesday, December 3, 2013 10:11:56 PM UTC, JonathanRRogers wrote: > > andrea crotti wrote: > > > > Argh true I missed that, I expected that jenkins would have quoted the > > spaces since it lets me enter them, is that a known issue than? > > I'll try without tomorrow, thanks > > > > First, is the script in question in an "Execute shell" block? Second, is > your script doing anything with the Jenkins project (job) name? Third, > in what context would you expect the name of the job to be quoted? > Without knowing the context, it's impossible to answer the question > usefully since many factors can affect how spaces are handled, escaped > or quoted, especially when a shell is involved. > > -- > Jonathan Rogers > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
