Build it once and use the build artifacts in the 40 tests. Maybe the tests also need to be build artifacts.
If the nodes you have have multiple executors, you can save by having a clone of the git repo somewhere on the node disk. Git plugin can utilize git --reference option which saves space -- Sami Albert Callarisa <shark...@gmail.com> kirjoitti 22.3.2012 kello 17.23: > Hi all, > > I am creating a distributed build using multiconfiguration project. Basically > I have an axis with a environment variable like 1, 2, 3... up to 40, so it > creates 40 builds. In a script of the build, I split the files to test in 40 > parts and each build setup runs one of those parts. > Also I have N nodes (14 currently) and they take each part, plus one more > part called 'master' that manages everything. > > The code of the project is in git, so initially the master node clones or > fetch the changes into the workspace. Then it triggers 40 build and everytime > a node takes one build, the workspace is in a different folder, so they clone > the repo 40 times... > I'm trying to solve it but I'm not sure if it's possible to do easily. I was > about to create 40 symbolic links in each node to make all the combinations > use the same folder, so it will pull instead of clone, but it's a bit hacky :P > Also I tried the plugin to copy files to the slave nodes but it runs after > the git clone in the slave, so it doesn't work for me. > > Any idea on how to fix it? > > Thanks!
