Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-7600

Add support for building a specific changeset

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • mercurial-plugin
    • None

      I have a parameterized job that asks the user which changeset he wants to build.

      The Mercurial plugin claims to support only branch names in 'Source Code Management -> Branch'. If I supply a changeset instead, it usually works, notwithstanding.

      The only caveat is: If said changeset already exists in the local workspace repository, Hudson will build the most recent changeset, not the one I asked for.

          [JENKINS-7600] Add support for building a specific changeset

          Jesse Glick added a comment -

          Possibly duplicate.

          Jesse Glick added a comment - Possibly duplicate.

          Elifarley added a comment -

          IMHO JENKINS-7600 is not a duplicate of JENKINS-5396, because the latter deals with the problems that arise if you specify a tag, while the former deals with specific changesets. At most, they are related, but not duplicates.

          Elifarley added a comment - IMHO JENKINS-7600 is not a duplicate of JENKINS-5396 , because the latter deals with the problems that arise if you specify a tag, while the former deals with specific changesets. At most, they are related, but not duplicates.

          We've similar needs : due to our development workflow using mercurial we may push several heads at once (or during a period of time lower than time needed for a test job) but we want jenkins to start test on every heads.

          I've made a pull request some time ago allowing this but it has not been integrated and any feedback or help to get it in would be welcome: https://github.com/jenkinsci/mercurial-plugin/pull/72

          Sylvain Thénault added a comment - We've similar needs : due to our development workflow using mercurial we may push several heads at once (or during a period of time lower than time needed for a test job) but we want jenkins to start test on every heads. I've made a pull request some time ago allowing this but it has not been integrated and any feedback or help to get it in would be welcome: https://github.com/jenkinsci/mercurial-plugin/pull/72

            kohsuke Kohsuke Kawaguchi
            elifarley Elifarley
            Votes:
            2 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: