In a matrix build, the following warning is printed, if you don't opt for 
"Always Force Sync", or "Clean Workspace":

"This is a matrix build; It is HIGHLY recommended that you enable the 'Always 
Force Sync' or 'Clean Workspace' options. Failing to do so will likely result 
in child builds not being synced properly."


I'm just wondering why this is? AFAICS, multiple *separate* clients are used - 
for the top-level "build" and all of the child builds which are spawned off 
that. I would have thought that each client would properly take care of its own 
state. Why would they not be synced properly? For example, for a matrix build 
called "Blah", with a configuration axis called "TYPE", with values "Release" 
and "Debug", there would be a top-level client "Blah", and child clients 
"Blah-TYPE-Release" and "Blah-TYPE-Debug". All the logged Perforce commands for 
these clients *look* reasonable, AFAICS, and not likely to cause syncing issues 
between clients and the server. So what is the issue here? Why are child builds 
likely not to be synced properly? Is it something to do with the child builds 
possibly being done on nodes on different machines, for different runs? If so, 
wouldn't this same issue affect normal non-matrix builds too?


Thanks,


-- Jonathan

-- 
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/d/optout.

Reply via email to