It's a dumb mistake. We tested our Jenkins backup mechanism but forgot shutting it down.
Sorry for asking such a stupid question. 李大明於 2015年2月26日星期四 UTC+8下午5時51分17秒寫道： > > I have a Jenkins server which runs build verification by Gerrit Trigger > plugin. > > This worked fine for months. But after last time I restart my Jenkins, > strange behavior happens: > > Each Gerrit uploaded patchset will trigger two build. One is correct, but > the other use the build ID. Like: > > > Jenkins > Patch Set 1: Build Started http://server/job/linux_verify/291/ > Patch Set 1: Build Started http://server/job/linux_verify/166/ > > In Jenkins WebUI I only see build 291 running but I got error like > > Fatal: Unable to create > '/home/jenkins/jenkins_slave/workspace/linux_verify/kernel/linux/linux-3.10.0/.git/index.lock': > File exists. > > > This means I have two git processes accessing the same repository. > > > I try to restart Jenkins server and slave node, also try to reconnect > GerritTrigger servers. > > None of this work. > > > Anyone have idea? > > > > > > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b4b161f4-5b88-4529-930d-52f5872b9ab3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
