com.atlassian.bamboo.repository.RepositoryException: Failed to get changes: Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4

Atlassian JIRA | Johannes Stamminger | 10 years ago
  1. 0

    While one plan was executing I tried creation of a new one. After having pressed the "Continue" button on the perforce repository details page, the ui was blocked, no interaction any longer possible with the bamboo. In the logfiles I detected entries like INFO | jvm 1 | 2007/03/06 13:37:17 | /usr/local/bin/p4 -u <perforce user> -p <perforce server>:<perforce port> -c <perforce clientspec name> client -o occuring repeatedly multiple times per second (!) without any further error message. Maybe it was not the best idea but I renamed the p4-executable (the morning after a stop-start I had loss of data so I tried to avoid this - but this is a different story). After some time (not immediately!) this perforce server penetration stopped with INFO | jvm 1 | 2007/03/06 14:20:37 | com.atlassian.bamboo.repository.RepositoryException: Failed to get changes: Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | INFO | jvm 1 | 2007/03/06 14:20:37 | at com.atlassian.bamboo.repository.perforce.PerforceRepository.getChangesSinceLastBuild(PerforceRepository.java:290) INFO | jvm 1 | 2007/03/06 14:20:37 | at com.atlassian.bamboo.build.strategy.PollingBuildStrategy.requiresBuild(PollingBuildStrategy.java:126) INFO | jvm 1 | 2007/03/06 14:20:37 | at com.atlassian.bamboo.build.DefaultBuildChangeDetector.checkIfBuildNeedsBuilding(DefaultBuildChangeDetector.java:166) INFO | jvm 1 | 2007/03/06 14:20:37 | at com.atlassian.bamboo.build.DefaultBuildChangeDetector.doTask(DefaultBuildChangeDetector.java:114) INFO | jvm 1 | 2007/03/06 14:20:37 | at com.atlassian.bamboo.build.DefaultBuildChangeDetector.run(DefaultBuildChangeDetector.java:77) INFO | jvm 1 | 2007/03/06 14:20:37 | at edu.emory.mathcs.backport.java.util.concurrent.helpers.ThreadHelpers$1.run(ThreadHelpers.java:34) INFO | jvm 1 | 2007/03/06 14:20:37 | at java.lang.Thread.run(Thread.java:595) Though bamboo itself still claims itself as running. After stop & start all seems to be fine again (seems no data lost). Note 1: there was currently executing another plan Note 2: after re-doing same steps again this did not re-occur. But I noticed by way of a failed build that to my fault the perforce depot referring to in the plan config was not yet included in the perforce client spec. (may be those aspects are related to this issue)

    Atlassian JIRA | 10 years ago | Johannes Stamminger
    com.atlassian.bamboo.repository.RepositoryException: Failed to get changes: Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4
  2. 0

    While one plan was executing I tried creation of a new one. After having pressed the "Continue" button on the perforce repository details page, the ui was blocked, no interaction any longer possible with the bamboo. In the logfiles I detected entries like INFO | jvm 1 | 2007/03/06 13:37:17 | /usr/local/bin/p4 -u <perforce user> -p <perforce server>:<perforce port> -c <perforce clientspec name> client -o occuring repeatedly multiple times per second (!) without any further error message. Maybe it was not the best idea but I renamed the p4-executable (the morning after a stop-start I had loss of data so I tried to avoid this - but this is a different story). After some time (not immediately!) this perforce server penetration stopped with INFO | jvm 1 | 2007/03/06 14:20:37 | com.atlassian.bamboo.repository.RepositoryException: Failed to get changes: Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | Cannot find executable at /usr/local/bin/p4 INFO | jvm 1 | 2007/03/06 14:20:37 | INFO | jvm 1 | 2007/03/06 14:20:37 | at com.atlassian.bamboo.repository.perforce.PerforceRepository.getChangesSinceLastBuild(PerforceRepository.java:290) INFO | jvm 1 | 2007/03/06 14:20:37 | at com.atlassian.bamboo.build.strategy.PollingBuildStrategy.requiresBuild(PollingBuildStrategy.java:126) INFO | jvm 1 | 2007/03/06 14:20:37 | at com.atlassian.bamboo.build.DefaultBuildChangeDetector.checkIfBuildNeedsBuilding(DefaultBuildChangeDetector.java:166) INFO | jvm 1 | 2007/03/06 14:20:37 | at com.atlassian.bamboo.build.DefaultBuildChangeDetector.doTask(DefaultBuildChangeDetector.java:114) INFO | jvm 1 | 2007/03/06 14:20:37 | at com.atlassian.bamboo.build.DefaultBuildChangeDetector.run(DefaultBuildChangeDetector.java:77) INFO | jvm 1 | 2007/03/06 14:20:37 | at edu.emory.mathcs.backport.java.util.concurrent.helpers.ThreadHelpers$1.run(ThreadHelpers.java:34) INFO | jvm 1 | 2007/03/06 14:20:37 | at java.lang.Thread.run(Thread.java:595) Though bamboo itself still claims itself as running. After stop & start all seems to be fine again (seems no data lost). Note 1: there was currently executing another plan Note 2: after re-doing same steps again this did not re-occur. But I noticed by way of a failed build that to my fault the perforce depot referring to in the plan config was not yet included in the perforce client spec. (may be those aspects are related to this issue)

    Atlassian JIRA | 10 years ago | Johannes Stamminger
    com.atlassian.bamboo.repository.RepositoryException: Failed to get changes: Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4
  3. 0

    h3. Summary Bamboo Cloud shows "not valid: is this a git repository" system errors. It occurs when Bamboo runs the command {{/usr/bin/git ls-remote}} to check the remote Bitbucket repositories. {noformat} com.atlassian.bamboo.repository.RepositoryException: com.atlassian.bamboo.plugins.git.GitCommandException: command /usr/bin/git ls-remote https://s********s:********@bitbucket.org/s********s/pjh-elect failed with code 128. Working directory was [.]., stderr: fatal: https://s********s:********@bitbucket.org/s********s/p*******/info/refs not valid: is this a git repository? at com.atlassian.bamboo.plugins.git.GitRepository.collectChangesSinceLastBuild(GitRepository.java:314) at com.atlassian.bamboo.plugins.git.GitRepository.collectChangesSinceLastBuild(GitRepository.java:237) .... Caused by: com.atlassian.bamboo.plugins.git.GitCommandException: command /usr/bin/git ls-remote https://s********s:********@bitbucket.org/s********s/p****** failed with code 128. Working directory was [.]., stderr: fatal: https://s********s:********@bitbucket.org/s********s/p*******/info/refs not valid: is this a git repository? at com.atlassian.bamboo.plugins.git.GitCommandProcessor.runCommand(GitCommandProcessor.java:587) at com.atlassian.bamboo.plugins.git.GitCommandProcessor.getRemoteRefs(GitCommandProcessor.java:430) at com.atlassian.bamboo.plugins.git.NativeGitOperationHelper$1.call(NativeGitOperationHelper.java:501) {noformat} The errors are intermittent and checking at a latter time will work again. h3. Environment * Bamboo * Bitbucket Cloud h3. Steps to reproduce: # Configure a "Bitbucket Cloud" repository under "Linked repositories" # Wait for at least 24 hours so Bamboo does multiple checks on the repositories. *Result:* The errors will appear of sporadic connection failures to Bitbucket on the section: /builds/admin/systemErrors.action h3. Workaround If the error is shown when running a build, try at a later time. Because the error is intermittent, if errors are found on the System Errors section, it can be discarded

    Atlassian JIRA | 11 months ago | Muhammad Fahd [Atlassian]
    com.atlassian.bamboo.repository.RepositoryException: com.atlassian.bamboo.plugins.git.GitCommandException: command /usr/bin/git ls-remote https://s********s:********@bitbucket.org/s********s/pjh-elect failed with code 128. Working directory was [.]., stderr: fatal: https://s********s:********@bitbucket.org/s********s/p*******/info/refs not valid: is this a git repository?
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    In the latest version of bamboo 5.5.1 we use the sshd version 0.8 which does not support key renegotiation. Now the later versions of Stash 3.1.0 uses sshd 0.11 which supports that. This caused issues in Bamboo when we try to clone large repositories from stash. Errors like below are thrown in the logs {code} 2014-06-30 14:28:46,524 ERROR [3-DelayedChangeDetectionThread:pool-7-thread-2] [ChainExecutionManagerImpl] Errors getting changes for HOG-NL-2 com.atlassian.bamboo.repository.RepositoryException: java.lang.RuntimeException: com.atlassian.bamboo.plugins.stash.repository.StashRepositoryException: com.atlassian.bamboo.repository.RepositoryException: : Cannot fetch branch 'refs/heads/master' from 'ssh://git@stash.sultan.network:7999/fen/testrepo.git' to source directory '/bamboo_data/xml-data/build-dir/_git-repositories-cache/f9f42cb46b34f29d4e0dcb7ae4acb47e96bd3d4c'. command /usr/bin/git fetch ssh://7ef786ec-d936-4fd8-8af5-90809410b1bd@127.0.0.1:44893/sultan/testrepo.git +refs/heads/master:refs/heads/master --update-head-ok failed with code 128. Working directory was [/bamboo_data/xml-data/build-dir/_git-repositories-cache/f9f42cb46b34f29d4e0dcb7ae4acb47e96bd3d4c]., stderr: Warning: Permanently added '[127.0.0.1]:44893' (RSA) to the list of known hosts. fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed at com.atlassian.bamboo.v2.trigger.DefaultChangeDetectionManager.collectChangesSinceLastBuildInternal(DefaultChangeDetectionManager.java:373) at com.atlassian.bamboo.v2.trigger.DefaultChangeDetectionManager.collectChangesSinceRevisions(DefaultChangeDetectionManager.java:261) at com.atlassian.bamboo.v2.trigger.DefaultChangeDetectionManager.collectChangesSinceRevisions(DefaultChangeDetectionManager.java:160) at com.atlassian.bamboo.v2.trigger.DefaultChangeDetectionManager.collectAllChangesSinceLastBuild(DefaultChangeDetectionManager.java:126) at com.atlassian.bamboo.v2.trigger.ManualBuildDetectionAction.performDelayedChangeDetection(ManualBuildDetectionAction.java:173) at com.atlassian.bamboo.chains.ChainExecutionManagerImpl$2.getChainState(ChainExecutionManagerImpl.java:209) at com.atlassian.bamboo.chains.ChainExecutionManagerImpl.tryStartChainState(ChainExecutionManagerImpl.java:262) at com.atlassian.bamboo.chains.ChainExecutionManagerImpl.delayedStart(ChainExecutionManagerImpl.java:198) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:304) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy97.delayedStart(Unknown Source) at com.atlassian.bamboo.plan.PlanExecutionManagerImpl$1$1$1$1.run(PlanExecutionManagerImpl.java:401) at com.atlassian.bamboo.util.CacheAwareness.whileReadingThroughCaches(CacheAwareness.java:85) at com.atlassian.bamboo.util.CacheAwareness.whileReadingThroughCaches(CacheAwareness.java:102) at com.atlassian.bamboo.plan.PlanExecutionManagerImpl$1$1$1.call(PlanExecutionManagerImpl.java:396) at com.atlassian.bamboo.plan.PlanExecutionManagerImpl$1$1$1.call(PlanExecutionManagerImpl.java:390) at com.atlassian.util.concurrent.ManagedLocks$ManagedLockImpl.withLock(ManagedLocks.java:312) at com.atlassian.bamboo.plan.PlanExecutionLockServiceImpl.lock(PlanExecutionLockServiceImpl.java:81) at com.atlassian.bamboo.plan.PlanExecutionManagerImpl.doWithProcessLock(PlanExecutionManagerImpl.java:741) at com.atlassian.bamboo.plan.PlanExecutionManagerImpl.access$200(PlanExecutionManagerImpl.java:125) at com.atlassian.bamboo.plan.PlanExecutionManagerImpl$1$1.run(PlanExecutionManagerImpl.java:384) at com.atlassian.bamboo.utils.BambooRunnables$1.run(BambooRunnables.java:49) at com.atlassian.bamboo.security.ImpersonationHelper.runWith(ImpersonationHelper.java:31) at com.atlassian.bamboo.security.ImpersonationHelper.runWithSystemAuthority(ImpersonationHelper.java:20) at com.atlassian.bamboo.security.ImpersonationHelper$1.run(ImpersonationHelper.java:52) at java.lang.Thread.run(Unknown Source) {code}

    Atlassian JIRA | 2 years ago | Sultan Maiyaki [Atlassian]
    com.atlassian.bamboo.repository.RepositoryException: java.lang.RuntimeException: com.atlassian.bamboo.plugins.stash.repository.StashRepositoryException: com.atlassian.bamboo.repository.RepositoryException: : Cannot fetch branch 'refs/heads/master' from 'ssh://git@stash.sultan.network:7999/fen/testrepo.git' to source directory '/bamboo_data/xml-data/build-dir/_git-repositories-cache/f9f42cb46b34f29d4e0dcb7ae4acb47e96bd3d4c'. command /usr/bin/git fetch ssh://7ef786ec-d936-4fd8-8af5-90809410b1bd@127.0.0.1:44893/sultan/testrepo.git +refs/heads/master:refs/heads/master --update-head-ok failed with code 128. Working directory was [/bamboo_data/xml-data/build-dir/_git-repositories-cache/f9f42cb46b34f29d4e0dcb7ae4acb47e96bd3d4c]., stderr: Warning: Permanently added '[127.0.0.1]:44893' (RSA) to the list of known hosts. fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed
  6. 0

    In the latest version of bamboo 5.5.1 we use the sshd version 0.8 which does not support key renegotiation. Now the later versions of Stash 3.1.0 uses sshd 0.11 which supports that. This caused issues in Bamboo when we try to clone large repositories from stash. Errors like below are thrown in the logs {code} 2014-06-30 14:28:46,524 ERROR [3-DelayedChangeDetectionThread:pool-7-thread-2] [ChainExecutionManagerImpl] Errors getting changes for HOG-NL-2 com.atlassian.bamboo.repository.RepositoryException: java.lang.RuntimeException: com.atlassian.bamboo.plugins.stash.repository.StashRepositoryException: com.atlassian.bamboo.repository.RepositoryException: : Cannot fetch branch 'refs/heads/master' from 'ssh://git@stash.sultan.network:7999/fen/testrepo.git' to source directory '/bamboo_data/xml-data/build-dir/_git-repositories-cache/f9f42cb46b34f29d4e0dcb7ae4acb47e96bd3d4c'. command /usr/bin/git fetch ssh://7ef786ec-d936-4fd8-8af5-90809410b1bd@127.0.0.1:44893/sultan/testrepo.git +refs/heads/master:refs/heads/master --update-head-ok failed with code 128. Working directory was [/bamboo_data/xml-data/build-dir/_git-repositories-cache/f9f42cb46b34f29d4e0dcb7ae4acb47e96bd3d4c]., stderr: Warning: Permanently added '[127.0.0.1]:44893' (RSA) to the list of known hosts. fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed at com.atlassian.bamboo.v2.trigger.DefaultChangeDetectionManager.collectChangesSinceLastBuildInternal(DefaultChangeDetectionManager.java:373) at com.atlassian.bamboo.v2.trigger.DefaultChangeDetectionManager.collectChangesSinceRevisions(DefaultChangeDetectionManager.java:261) at com.atlassian.bamboo.v2.trigger.DefaultChangeDetectionManager.collectChangesSinceRevisions(DefaultChangeDetectionManager.java:160) at com.atlassian.bamboo.v2.trigger.DefaultChangeDetectionManager.collectAllChangesSinceLastBuild(DefaultChangeDetectionManager.java:126) at com.atlassian.bamboo.v2.trigger.ManualBuildDetectionAction.performDelayedChangeDetection(ManualBuildDetectionAction.java:173) at com.atlassian.bamboo.chains.ChainExecutionManagerImpl$2.getChainState(ChainExecutionManagerImpl.java:209) at com.atlassian.bamboo.chains.ChainExecutionManagerImpl.tryStartChainState(ChainExecutionManagerImpl.java:262) at com.atlassian.bamboo.chains.ChainExecutionManagerImpl.delayedStart(ChainExecutionManagerImpl.java:198) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:304) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy97.delayedStart(Unknown Source) at com.atlassian.bamboo.plan.PlanExecutionManagerImpl$1$1$1$1.run(PlanExecutionManagerImpl.java:401) at com.atlassian.bamboo.util.CacheAwareness.whileReadingThroughCaches(CacheAwareness.java:85) at com.atlassian.bamboo.util.CacheAwareness.whileReadingThroughCaches(CacheAwareness.java:102) at com.atlassian.bamboo.plan.PlanExecutionManagerImpl$1$1$1.call(PlanExecutionManagerImpl.java:396) at com.atlassian.bamboo.plan.PlanExecutionManagerImpl$1$1$1.call(PlanExecutionManagerImpl.java:390) at com.atlassian.util.concurrent.ManagedLocks$ManagedLockImpl.withLock(ManagedLocks.java:312) at com.atlassian.bamboo.plan.PlanExecutionLockServiceImpl.lock(PlanExecutionLockServiceImpl.java:81) at com.atlassian.bamboo.plan.PlanExecutionManagerImpl.doWithProcessLock(PlanExecutionManagerImpl.java:741) at com.atlassian.bamboo.plan.PlanExecutionManagerImpl.access$200(PlanExecutionManagerImpl.java:125) at com.atlassian.bamboo.plan.PlanExecutionManagerImpl$1$1.run(PlanExecutionManagerImpl.java:384) at com.atlassian.bamboo.utils.BambooRunnables$1.run(BambooRunnables.java:49) at com.atlassian.bamboo.security.ImpersonationHelper.runWith(ImpersonationHelper.java:31) at com.atlassian.bamboo.security.ImpersonationHelper.runWithSystemAuthority(ImpersonationHelper.java:20) at com.atlassian.bamboo.security.ImpersonationHelper$1.run(ImpersonationHelper.java:52) at java.lang.Thread.run(Unknown Source) {code}

    Atlassian JIRA | 2 years ago | Sultan Maiyaki [Atlassian]
    com.atlassian.bamboo.repository.RepositoryException: java.lang.RuntimeException: com.atlassian.bamboo.plugins.stash.repository.StashRepositoryException: com.atlassian.bamboo.repository.RepositoryException: : Cannot fetch branch 'refs/heads/master' from 'ssh://git@stash.sultan.network:7999/fen/testrepo.git' to source directory '/bamboo_data/xml-data/build-dir/_git-repositories-cache/f9f42cb46b34f29d4e0dcb7ae4acb47e96bd3d4c'. command /usr/bin/git fetch ssh://7ef786ec-d936-4fd8-8af5-90809410b1bd@127.0.0.1:44893/sultan/testrepo.git +refs/heads/master:refs/heads/master --update-head-ok failed with code 128. Working directory was [/bamboo_data/xml-data/build-dir/_git-repositories-cache/f9f42cb46b34f29d4e0dcb7ae4acb47e96bd3d4c]., stderr: Warning: Permanently added '[127.0.0.1]:44893' (RSA) to the list of known hosts. fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. com.atlassian.bamboo.repository.RepositoryException

      Failed to get changes: Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4 Cannot find executable at /usr/local/bin/p4

      at com.atlassian.bamboo.repository.perforce.PerforceRepository.getChangesSinceLastBuild()
    2. com.atlassian.bamboo
      DefaultBuildChangeDetector.run
      1. com.atlassian.bamboo.repository.perforce.PerforceRepository.getChangesSinceLastBuild(PerforceRepository.java:290)
      2. com.atlassian.bamboo.build.strategy.PollingBuildStrategy.requiresBuild(PollingBuildStrategy.java:126)
      3. com.atlassian.bamboo.build.DefaultBuildChangeDetector.checkIfBuildNeedsBuilding(DefaultBuildChangeDetector.java:166)
      4. com.atlassian.bamboo.build.DefaultBuildChangeDetector.doTask(DefaultBuildChangeDetector.java:114)
      5. com.atlassian.bamboo.build.DefaultBuildChangeDetector.run(DefaultBuildChangeDetector.java:77)
      5 frames
    3. Backport of JSR 166
      ThreadHelpers$1.run
      1. edu.emory.mathcs.backport.java.util.concurrent.helpers.ThreadHelpers$1.run(ThreadHelpers.java:34)
      1 frame
    4. Java RT
      Thread.run
      1. java.lang.Thread.run(Thread.java:595)
      1 frame