Hi John, your approach sounds interesting. Could you please share some Workflow code that shows how you compute the Workspace location, use ws(), and pass workspace locations to subsequent jobs?
When accessing workspaces in Workflow you're also facing the problem of concurrent runs. How do you deal with that? Thanks in advance! Greetings, Thomas On Wednesday, December 30, 2015 at 3:11:46 AM UTC+1, Martin d'Anjou wrote: > > On Wednesday, December 23, 2015 at 9:45:57 PM UTC-5, John D. Ament wrote: >> >> Hi, >> >> I was wondering if anyone had any best practices or tips to share on have >> a common workspace for a pipeline job. >> > > I use Workflow job definitions, and I compute the location of the > workspace in each job of the build chain before the actual build actions > take place, using the ws() built step. Subsequent jobs in the build chain > use the same workspace (the location can be computed). Subsequent jobs need > not to be in the same workflow definition, nor in a formal pipeline (I do > not use triggers nor pipeline plugins). I have enough input parameters for > the subsequent jobs in the chain to locate the workspace of the previous > job. I do not move nor archive data (I have thousands of files and > gigabytes of data over NFS so I don't want to spend time moving it or > archiving/extracting it). > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/8724e85d-36e2-4e1d-a920-f9047587aada%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
