Re: shared workspace
For this then you should be able to use the Copy artifact plugin . - Original Message - From: Liora Milbaum li...@lmb.co.il To: jenkinsci-users@googlegroups.com Sent: Wednesday, January 8, 2014 1:01:17 AM Subject: Re: shared workspace Thanks for the input. The symbolic link option is not available as some of my build servers are Windows XP. The reason I need a shared workspace is for sharing build artifacts, like dlls (generated by multiple jobs on multiple slaves). Are there other options implementing such a build schema? Liora On Tuesday, January 7, 2014 1:00:35 PM UTC+2, Liora Milbaum wrote: I am using Jenkins on Windows. Trying to implement a MultiJob project which executes on few nodes. How can I share the same workspace for all jobs in the MultiJob Project? Thanks, Liora -- 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 . -- 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.
Re: shared workspace
Right, the solution to this problem is not to share the workspace, but instead to archive the important artifacts from each job (onto the Jenkins master) and then configure downstream jobs to retrieve them. This is a far more reliable solution as well, as it allows job to be re-run, and for jobs to run in parallel without fear of corrupting the workspace. - Original Message - From: jenkinsci-users@googlegroups.com To: jenkinsci-users@googlegroups.com At: Jan 8 2014 08:25:57 For this then you should be able to use the Copy artifact plugin. From: Liora Milbaum li...@lmb.co.il To: jenkinsci-users@googlegroups.com Sent: Wednesday, January 8, 2014 1:01:17 AM Subject: Re: shared workspace Thanks for the input. The symbolic link option is not available as some of my build servers are Windows XP. The reason I need a shared workspace is for sharing build artifacts, like dlls (generated by multiple jobs on multiple slaves). Are there other options implementing such a build schema? Liora On Tuesday, January 7, 2014 1:00:35 PM UTC+2, Liora Milbaum wrote: I am using Jenkins on Windows. Trying to implement a MultiJob project which executes on few nodes. How can I share the same workspace for all jobs in the MultiJob Project? Thanks, Liora -- 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. -- 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. -- 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.
Re: shared workspace
On Wed, Jan 8, 2014 at 1:01 AM, Liora Milbaum li...@lmb.co.il wrote: Thanks for the input. The symbolic link option is not available as some of my build servers are Windows XP. The reason I need a shared workspace is for sharing build artifacts, like dlls (generated by multiple jobs on multiple slaves). Are there other options implementing such a build schema? The 'copy artifact' plugin can retrieve things built in other jobs. Or there are ways to publish results in various ways, all of which may be tricky to manage if you want to reuse the artifact versions currently being built in the same matrix job run. We use subversion and generally split the libraries out to their own project levels so you can separately control the revisions pulled into the consuming projects with svn externals. This doesn't take any specific jenkins support and will work the same with manual checkouts and builds. -- Les Mikesell lesmikes...@gmail.com -- 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.
shared workspace
I am using Jenkins on Windows. Trying to implement a MultiJob project which executes on few nodes. How can I share the same workspace for all jobs in the MultiJob Project? Thanks, Liora -- 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.
Re: shared workspace
I was able to do this by getting a network location set up and then using symlinks on the slave machines as the workspace directory that point to that network location. - Original Message - From: Liora Milbaum li...@lmb.co.il To: jenkinsci-users@googlegroups.com Sent: Tuesday, January 7, 2014 5:00:35 AM Subject: shared workspace I am using Jenkins on Windows. Trying to implement a MultiJob project which executes on few nodes. How can I share the same workspace for all jobs in the MultiJob Project? Thanks, Liora -- 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 . -- 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.
Re: shared workspace
On Tue, Jan 7, 2014 at 9:36 AM, k.thiel...@comcast.net wrote: I was able to do this by getting a network location set up and then using symlinks on the slave machines as the workspace directory that point to that network location. Did it turn out to be a good idea? A matrix job is not going to protect your files from concurrent access. Normally you'd want independent checkouts of the source and 'archive artifcacts' to consolidate the results back on the master. -- Les Mikesell lesmikes...@gmail.com -- 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.
Re: shared workspace
It works for what we need it for, which actually isn't matrix jobs. Our setup was more in an interest of saving space and not having to keep expanding VM hard disk space as jobs are added. With a much larger network location storage space we can have multiple smaller slaves to handle the job load. We also use SVN with the emulate fresh checkout option so a lot of the workspace is already there for all the slaves. Again it works for what we need it for, it may not work for everyone else's setup necessarily. - Original Message - From: Les Mikesell lesmikes...@gmail.com To: jenkinsci-users jenkinsci-users@googlegroups.com Sent: Tuesday, January 7, 2014 10:04:19 AM Subject: Re: shared workspace On Tue, Jan 7, 2014 at 9:36 AM, k.thiel...@comcast.net wrote: I was able to do this by getting a network location set up and then using symlinks on the slave machines as the workspace directory that point to that network location. Did it turn out to be a good idea? A matrix job is not going to protect your files from concurrent access. Normally you'd want independent checkouts of the source and 'archive artifcacts' to consolidate the results back on the master. -- Les Mikesell lesmikes...@gmail.com -- 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. -- 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.
Re: shared workspace
On Tue, Jan 7, 2014 at 11:00 AM, k.thiel...@comcast.net wrote: It works for what we need it for, which actually isn't matrix jobs. Our setup was more in an interest of saving space and not having to keep expanding VM hard disk space as jobs are added. With a much larger network location storage space we can have multiple smaller slaves to handle the job load. We also use SVN with the emulate fresh checkout option so a lot of the workspace is already there for all the slaves. Again it works for what we need it for, it may not work for everyone else's setup necessarily. I wouldn't expect it to work well for typical matrix jobs unless the jobs don't actually use the same files (in which case there isn't much point in trying to share them) or something within the job itself arbitrates the concurrent access. We do use some network mapping for read-only access to a common set of tools and libraries, but write everything locally - on VMs the workspace is on a separate volume that can be rebuild as needed instead of having to expand a disk in place. Even if we used network mapped workspace, I'd keep it unique per slave to avoid any contention. -- Les Mikesell lesmikes...@gmail.com -- 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.
Re: shared workspace
Thanks for the input. The symbolic link option is not available as some of my build servers are Windows XP. The reason I need a shared workspace is for sharing build artifacts, like dlls (generated by multiple jobs on multiple slaves). Are there other options implementing such a build schema? Liora On Tuesday, January 7, 2014 1:00:35 PM UTC+2, Liora Milbaum wrote: I am using Jenkins on Windows. Trying to implement a MultiJob project which executes on few nodes. How can I share the same workspace for all jobs in the MultiJob Project? Thanks, Liora -- 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.
