Mercurial updates on matrix projects aren't synced properly

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • Component/s: mercurial-plugin
    • None
    • Environment:
      Platform: All, OS: All

      ... unlike CVS and Subversion, which uses the build timestamp, Mercurial check
      out doesn't use any anchor. Because of this, in a matrix project, each
      configuration build may end up seeing a different changeset.

      We need to generalize this so that SCM can pass some anchor information across
      different builds, so that each SCM doesn't have to hard-code against matrix
      projects.

            Assignee:
            Willem Verstraeten
            Reporter:
            Kohsuke Kawaguchi
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: