gocd: "Modification check failed for material" during 'git config remote.origin.url'

Hello,

I’m having a material check failure and Go isn’t giving any clear reason for it.

On the Go interface we have the following:

Modification check failed for material: URL: git@bitbucket.org:teamname/repository.git, Branch: topic [Jan-27 16:52:03]
Error performing command: --- Command --- git config remote.origin.url --- Environment --- {} --- INPUT ---- --OUTPUT --- --- ERROR --- ---

And on the log files:

2016-01-27 16:36:33,858  WARN [89@MessageListener for MaterialUpdateListener] MaterialDatabaseUpdater:121 - [Material Update] Modification check failed for material: URL: git@bitbucket.org:teamname/repository.git, Branch: topic
java.lang.RuntimeException: Error performing command: --- Command ---
git config remote.origin.url
--- Environment ---
{}
--- INPUT ----


--OUTPUT ---

--- ERROR ---

---

    at com.thoughtworks.go.util.ExceptionUtils.bomb(ExceptionUtils.java:40)
    at com.thoughtworks.go.config.materials.git.GitMaterial.getGit(GitMaterial.java:189)
    at com.thoughtworks.go.config.materials.git.GitMaterial.modificationsSince(GitMaterial.java:109)
    at com.thoughtworks.go.server.service.materials.GitPoller.modificationsSince(GitPoller.java:36)
    at com.thoughtworks.go.server.service.materials.GitPoller.modificationsSince(GitPoller.java:27)
    at com.thoughtworks.go.server.service.MaterialService.modificationsSince(MaterialService.java:110)
    at com.thoughtworks.go.server.materials.ScmMaterialUpdater.insertLatestOrNewModifications(ScmMaterialUpdater.java:57)
    at com.thoughtworks.go.server.materials.MaterialDatabaseUpdater.insertLatestOrNewModifications(MaterialDatabaseUpdater.java:155)
    at com.thoughtworks.go.server.materials.MaterialDatabaseUpdater.updateMaterialWithNewRevisions(MaterialDatabaseUpdater.java:147)
    at com.thoughtworks.go.server.materials.MaterialDatabaseUpdater$2.doInTransaction(MaterialDatabaseUpdater.java:110)
    at com.thoughtworks.go.server.transaction.TransactionCallback.doWithExceptionHandling(TransactionCallback.java:24)
    at com.thoughtworks.go.server.transaction.TransactionTemplate$3.doInTransaction(TransactionTemplate.java:53)
    at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:130)
    at com.thoughtworks.go.server.transaction.TransactionTemplate.executeWithExceptionHandling(TransactionTemplate.java:49)
    at com.thoughtworks.go.server.materials.MaterialDatabaseUpdater.updateMaterial(MaterialDatabaseUpdater.java:107)
    at com.thoughtworks.go.server.materials.MaterialUpdateListener.onMessage(MaterialUpdateListener.java:51)
    at com.thoughtworks.go.server.materials.MaterialUpdateListener.onMessage(MaterialUpdateListener.java:31)
    at com.thoughtworks.go.server.messaging.activemq.JMSMessageListenerAdapter.runImpl(JMSMessageListenerAdapter.java:65)
    at com.thoughtworks.go.server.messaging.activemq.JMSMessageListenerAdapter.run(JMSMessageListenerAdapter.java:50)
    at java.lang.Thread.run(Thread.java:745)
Caused by: com.thoughtworks.go.util.command.CommandLineException: Error performing command: --- Command ---
git config remote.origin.url
--- Environment ---
{}
--- INPUT ----


--OUTPUT ---

--- ERROR ---

---

    at com.thoughtworks.go.util.command.CommandLine.runOrBomb(CommandLine.java:498)
    at com.thoughtworks.go.util.command.CommandLine.runOrBomb(CommandLine.java:526)
    at com.thoughtworks.go.domain.materials.SCMCommand.runOrBomb(SCMCommand.java:42)
    at com.thoughtworks.go.domain.materials.git.GitCommand.workingRepositoryUrl(GitCommand.java:217)
    at com.thoughtworks.go.config.materials.git.GitMaterial.isRepositoryChanged(GitMaterial.java:232)
    at com.thoughtworks.go.config.materials.git.GitMaterial.git(GitMaterial.java:199)
    at com.thoughtworks.go.config.materials.git.GitMaterial.getGit(GitMaterial.java:187)
    ... 18 more

The repository/branch exists, and is accessible by the Go server. Pressing ‘Check Connection’ results in success.

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 18 (8 by maintainers)

Most upvoted comments

@mushycode , yes, it is because the flyweight directory ends up being corrupted. We may need to add a check to delete and reclone the flyweight directory in such a case.