Hi,
I am trying to get a build chain happening with a multijob phase plugin,
but having a problem getting the plugin to respect workspace location
directives.
Job1 uses a custom workspace called 'data'
The other jobs share the workspace, using the 'Build Environment -> Run
this job on the same node where another job -> Share same workspace'
checkbox.
Job1 deploys a base system file structure by wipe and pull from git in the
shared workspace. Node is set using Node build parameter.
Job2 deploys module1 by pull from git, running on same node as Job1 and
share its workspace
Job3 deploys module2 by pull from git, running on same node as Job1 and
share its workspace
Job4 symlinks the modules into the file structure, running on same node as
Job1 and share its workspace
Running these manually works perfectly. Each job runs in the same workspace
('data') and no other workspaces are created. On completion of Job4 I have
a fully deployed and working web server that I can symlink to the apache
web root.
Jobs 2 and 3 can be run in the same phase, so I created a new job to link
them together.
New job has the same custom workspace as Job1, and uses the same Node build
parameter.
Build step 1 Triggers a build of Job1 passing the same build parameters
Build step 2 Calls a Multijob phase building Job2 and Job3.
Build step 3 Triggers a build of Job4.
Problem is that Job2 and Job3 now run in their own workspaces. They do not
share the workspaces like the other jobs. I now get a folders created in
the workspace called Job1 and Job2 and the modules are pulled into the
respective folders.
I have tried various settings like 'Build on same node' and 'Current build
parameters', but nothing seems to fix the issue.
Workaround is to avoid the Multijob phase plugin and trigger each job as
separate sub-projects.
Any other options to fix this using the plugin?
Thanks,
Charlie
--
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/d/optout.
