Hi,
We use jenkins with one server and 3 slaves where the builds are done.
There are more than 40 jobs with configuration matrix (up to 16
configurations per job)
Our git repo is big, we cannot have a clone in each workspace.
For that reason on each slave, the repo is in a common directory for
all jobs
and the number of executors is set to 1 in each slave configuration.
Jobs were running fine since today without problems, but were run
manually.
We have just activated hourly git polling and jobs dependencies.
We sometimes get git errors on jobs because the git index is locked :
...
Caused by: hudson.plugins.git.GitException: Error performing
command: C:\Tools\git\bin\git checkout -f
5d155c48c30354d28e7c6b98b341f2514aabc4c5
10:26:46 Command "C:\Tools\git\bin\git checkout -f
5d155c48c30354d28e7c6b98b341f2514aabc4c5" returned status code 128:
fatal: Unable to create 'C:/Projects/path/.git/index.lock': File
exists.
Fetching upstream changes from https://server/git/path.git
Commencing build of Revision
5d155c48c30354d28e7c6b98b341f2514aabc4c5 (origin/master)
Checking out Revision 5d155c48c30354d28e7c6b98b341f2514aabc4c5
(origin/master)
FATAL: Could not checkout null with start point
5d155c48c30354d28e7c6b98b341f2514aabc4c5
hudson.plugins.git.GitException: Could not checkout null with
start point 5d155c48c30354d28e7c6b98b341f2514aabc4c5
...
The problem is that several actions occurs at the same time in the
repo.
Git fetch is started on a node while another job is running even
though the number of executor is set to 1 on each slave.
Is there a way to prevent jenkins to perform any actions on a node
while a job is running ?
Thanks,
Bertrand.
