HG plugin should handle .hg dir not existsing in current directory

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • 2.7 rc1, 2.7
    • Affects Version/s: None
    • Component/s: Repository (Mercurial)
    • None
    • Environment:

      BEAC, HG

      This plan: https://bamboo.extranet.atlassian.com/browse/CRUCHG-CHAIN-FUNC-23
      failed due to:

      The build has failed to check out the source code: command [/usr/bin/hg, update, --clean, --rev, 8658647caaeafcada4c4486ed7b75a5b28dae95e, --config, ui.ssh=ssh -o "StrictHostKeyChecking=no" -i /tmp/bambooHg5093194156945601042.tmp] failed. stderr: abort: There is no Mercurial repository here (.hg not found)!
stdout: 
Error occurred while executing the build for CRUCHG-CHAIN-FUNC-23 : command [/usr/bin/hg, update, --clean, --rev, 8658647caaeafcada4c4486ed7b75a5b28dae95e, --config, ui.ssh=ssh -o "StrictHostKeyChecking=no" -i /tmp/bambooHg5093194156945601042.tmp] failed. stderr: abort: There is no Mercurial repository here (.hg not found)!
stdout:

      This was possibly caused by build CRUCHG-CHAIN-FUNC-22, that was manually stopped, and due to a forked running server, failed to delete the entire build directory.

      When the HG-Bamboo plugin runs, it should check the 'force clean build' flag, and delete the entire working directory if it exists.

      Also - the logging:

      Pulling from local cache repository to source directory

      should accurately reflect the exact HG command being executed. ie. either a pull or a clone ?

        1. bamboo-agent-72.private.atlassian.com_atlassian-bamboo.log.bz2
          128 kB
          AntonA

            Assignee:
            PiotrA
            Reporter:
            Nick
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: