Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-10453

Bamboo builds erroneously fail, seemingly at random, with bogus Perforce error on OSX agents

    XMLWordPrintable

Details

    • Bug
    • Resolution: Handled by Support
    • High
    • None
    • 3.2
    • Builds
    • None
    • Bamboo 3.2 build 2600
      Agent running OSX 10.6.6
      JDK on agent system: 1.6.0_29

    Description

      We have many Bamboo agents and projects on multiple OS configurations. Specifically when the agent is running on an OSX machine:

      Bamboo intermittently reports failures prior to building a stage, not necessarily the first stage, with the error message "Error occurred while executing the build for PROJECTAND-AGENTINFO-BUILDSTEPNAME-## : Unable to extract client root from Perforce, therefore could not evaluate where the source will be checked out to."

      When running the agent in console mode, no errors are reported when this happens. This happens intermittently but often, on every project built by the OSX agent. Perforce ticket expiration for the build account is a few days.

      The problem used to occur prior to a build's first stage after long periods of inactivity (say, coming back to work Monday morning). Now, however, it's happening to seemingly random steps at anytime. Sometimes retrying failed jobs succeeds, only to have the next stage fail. This intermittency, paired with a complete lack of ANY Perforce problems on the system outside of those Bamboo is reporting, leads me to believe that the reported error is inaccurate.

      I would like to ask (a) for help debugging this problem, and (b) that this error message never appear unless there actually is a problem with Perforce client retrieval, and that any other error report a more appropriate message.

      Attachments

        Activity

          People

            Unassigned Unassigned
            4dfa25b1-3bae-444f-9df4-903db9179ab7 Deleted Account (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: