Uploaded image for project: 'Bamboo'
  1. Bamboo
  2. BAM-8866

Bamboo not updating Mercurial sub-repositories when getting source on build server

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.0, 3.1
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Themes:
      DVCS
    • Last commented by user?:
      true
    • Story Points:
      2
    • Comments:
      9

      Description

      From SAC:
      "We use Mercurial and our project has a sub-repository (in a folder UI\Elegant) which is specified in the .hgsub file. The project is setup correctly, we can get it to any PC, commit, push, pull changes etc.. However, when changes to the sub-repository are made the Bamboo build fails. The hg.exe command appears to work in getting the project to the cache folder, though the sub-repository (UI\Elegant) is missing, but when it then tries to update the working folder (Bamboo\xml-data\build-dir\AIE-DEV-JOB1) it fails saying no working folder is specified for UI\Elegant.

      How can we resolve this?
      "
      https://support.atlassian.com/browse/BSP-4674

        Attachments

          Activity

          Hide
          anton@atlassian.com Anton Mazkovoi [Atlassian] added a comment -

          Hi Lars,

          We are investigating the solution and are trying to make this work for Bmaboo 3.3. At the moment we cannot guarantee this just yet.

          Cheers,
          Anton

          Show
          anton@atlassian.com Anton Mazkovoi [Atlassian] added a comment - Hi Lars, We are investigating the solution and are trying to make this work for Bmaboo 3.3. At the moment we cannot guarantee this just yet. Cheers, Anton
          Hide
          mwent Marek Went [Atlassian] added a comment - - edited

          Really 2 tasks:

          • make caching optional (easy one)
          • investigate if we can support repo caching for sub repositories (python changes)

          Implement 1, timebox 2 to 4h

          Show
          mwent Marek Went [Atlassian] added a comment - - edited Really 2 tasks: make caching optional (easy one) investigate if we can support repo caching for sub repositories (python changes) Implement 1, timebox 2 to 4h
          Hide
          sopel Steffen Opel [Utoolity] added a comment -

          This seems to affect me as well, albeit with a Git sub-repository within a Mercurial repository. The error signature pretty much resembles the one reported by Simon Stebbing, so I'll omit the log for the moment, let me know if you'd still like to see it.

          Alternatively you could test this yourself: The Mercurial repository in question is actually a Bamboo Plugin hosted at Bitbucket, the Git sub-repository has been introduced with release 1.4.0 and triggered the first failed build of this Bamboo plugin on our Bamboo server

          Is the fix mentioned in the initial comment a viable workaround I could integrate myself eventually, i.e. should I open a respective support request?

          Thanks much,
          Steffen

          Show
          sopel Steffen Opel [Utoolity] added a comment - This seems to affect me as well, albeit with a Git sub-repository within a Mercurial repository. The error signature pretty much resembles the one reported by Simon Stebbing , so I'll omit the log for the moment, let me know if you'd still like to see it. Alternatively you could test this yourself: The Mercurial repository in question is actually a Bamboo Plugin hosted at Bitbucket, the Git sub-repository has been introduced with release 1.4.0 and triggered the first failed build of this Bamboo plugin on our Bamboo server Is the fix mentioned in the initial comment a viable workaround I could integrate myself eventually, i.e. should I open a respective support request? Thanks much, Steffen
          Hide
          lueschem Matthias Luescher added a comment -

          If you have a fairly recent version of mercurial there is a simple workaround which you can add to your .hgsub file of the top level repository:

          MYSUBREPO = MYSUBREPO

          [subpaths]

          1. bamboo workaround (subrepositories do not get cached correctly)!
            .*/_hg-repositories-cache/[a-zA-Z0-9] {40}

            /(.*) = https://MYSERVER/\1

          Using this workaround the requests to the subrepositories will get redirected to the server instead of the cache.

          Show
          lueschem Matthias Luescher added a comment - If you have a fairly recent version of mercurial there is a simple workaround which you can add to your .hgsub file of the top level repository: MYSUBREPO = MYSUBREPO [subpaths] bamboo workaround (subrepositories do not get cached correctly)! .*/_hg-repositories-cache/ [a-zA-Z0-9] {40} /(.*) = https://MYSERVER/\1 Using this workaround the requests to the subrepositories will get redirected to the server instead of the cache.
          Hide
          lueschem Matthias Luescher added a comment -

          The previous comment with some formatting:
          If you have a fairly recent version of mercurial there is a simple workaround which you can add to your .hgsub file of the top level repository:

          MYSUBREPO = MYSUBREPO
          
          [subpaths]
          # bamboo workaround (subrepositories do not get cached correctly)!
          .*/_hg-repositories-cache/[a-zA-Z0-9]{40}/(.*) = https://MYSERVER/\1
          

          Using this workaround the requests to the subrepositories will get redirected to the server instead of the cache.

          Show
          lueschem Matthias Luescher added a comment - The previous comment with some formatting: If you have a fairly recent version of mercurial there is a simple workaround which you can add to your .hgsub file of the top level repository: MYSUBREPO = MYSUBREPO [subpaths] # bamboo workaround (subrepositories do not get cached correctly)! .*/_hg-repositories-cache/[a-zA-Z0-9]{40}/(.*) = https://MYSERVER/\1 Using this workaround the requests to the subrepositories will get redirected to the server instead of the cache.

            People

            • Votes:
              4 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Last commented:
                3 years, 42 weeks, 6 days ago