Remote Mercurial trigger not working with .hg/hgrc [hook] setting "changegroup.update"

XMLWordPrintable

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Low
    • None
    • Affects Version/s: 6.7.2
    • Component/s: Repository (Mercurial)
    • None
    • 1
    • Severity 3 - Minor

      Issue Summary

      Environment

      Bamboo version 6.7.2 running and Mercurial version 5.1 (as of hg --version from command-line) being installed on Linux / MacOS.

      Steps to Reproduce

      1. Stand up a local Mercurial repository with source file(s) and connect it to e.g. TortopiseHg being used as Mercurial server.
      2. Add this Mercurial repository to a Bamboo build plan, either as a Linked repository or plan internally.
      3. Configure this build plan's "Remote trigger" to use the Mercurial repository and prepare it according to Repository triggers the build when changes are committed by copying the SVN postCommitBuildTrigger.sh script into your local repository folder and there edit .hg/hgrc adding
        [hooks]
        changegroup.update = /<path to script>/postCommitBuildTrigger.sh <Bamboo URL> <PROJ-BUILD key>
      1. Now modify at least one of the repository files and then hg add plus hg commit the change.

      Expected Results

      The build should automatically be triggered.

      Actual Results

      Build is not triggered. No error appears in the logs.

      Workaround

      Change the .hg/hgrc setting to this:

      [hooks]
      commit = /<path to script>/postCommitBuildTrigger.sh <Bamboo URL> <PROJ-BUILD key>

      and a hg commit immediately kicks off a build for the plan key pointed to.

              Assignee:
              Unassigned
              Reporter:
              Gerhard Forster (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: