Yes, it's possible in the advanced settings to override the build directory naming scheme, but it's also quite simple to just add a shell/batch script step to your job to copy the built files into the deployment location. You really would not want to use /var/www/public as a slave workspace directory, as Jenkins will put files in there that are unrelated to the build that is being performed (JAR files for necessary Java classes, etc.).
----- Original Message ----- From: [email protected] To: [email protected] At: Aug 21 2013 07:34:41 Hi, is it possible to copy a built on the slaves in a static folder? Jenkins itself generate the slaves name and project label as subfolders. The target of a slaves folder could be e.g. /var/www/public/ thank you Gregory-- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out. -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
