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

Stop changeset tags from being counted as a change in Mercurial Plugin polling

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      We have the slave build machines polling Mercurial repositories, using the Mercurial plugin, to trigger builds.
      During the Jenkins job, we create and push a tag changeset as part of the build process.
      This tag changeset is detected by polling and causing an infinite loop of builds.

      I've looked into other options, I notice the notice away from polling to be more push activated, which sounds good, but it seems this still relies on polling to detect what has changed, so it seems this would still be a problem.
      The other thing that sounded like it may help was "modules" in the Mercurial plugin, but this is a huge change to move lots of repositories to put everything except the hgtags file into a sub folder and then specify that sub folder as a module.

      If tag changesets were ignorred by polling, similar to a change that was made to ignore merge changesets, all would be good in the world

        Attachments

          Issue Links

            Activity

            Hide
            jglick Jesse Glick added a comment -

            Why would a change in .hgtags alone require a new build?

            Show
            jglick Jesse Glick added a comment - Why would a change in .hgtags alone require a new build?
            Hide
            janarb Jan Wittig added a comment -

            Because a new tag is created that needs to be build and deployed. I don't understand which advantage it should have to restrict the allowed possibilities of accepted changes without configuration option...

            Show
            janarb Jan Wittig added a comment - Because a new tag is created that needs to be build and deployed. I don't understand which advantage it should have to restrict the allowed possibilities of accepted changes without configuration option...
            Hide
            jglick Jesse Glick added a comment -

            a new tag is created that needs to be build and deployed

            The supported way of doing that would be a multibranch project using a tag head source.

            Show
            jglick Jesse Glick added a comment - a new tag is created that needs to be build and deployed The supported way of doing that would be a multibranch project using a tag head source.
            Hide
            janarb Jan Wittig added a comment -

            I'm not sure what you refer to. I found this one: https://docs.openstack.org/infra/jenkins-job-builder/project_workflow_multibranch.html stating experimental and no Mercurial support, so I guess you are probably talking about https://jenkins.io/blog/2015/12/03/pipeline-as-code-with-multibranch-workflows-in-jenkins/? Could you provide more details, please?

            Show
            janarb Jan Wittig added a comment - I'm not sure what you refer to. I found this one: https://docs.openstack.org/infra/jenkins-job-builder/project_workflow_multibranch.html stating experimental and no Mercurial support, so I guess you are probably talking about https://jenkins.io/blog/2015/12/03/pipeline-as-code-with-multibranch-workflows-in-jenkins/? Could you provide more details, please?
            Hide
            jglick Jesse Glick added a comment -

            Yes a Jenkins multibranch project.

            Show
            jglick Jesse Glick added a comment - Yes a Jenkins multibranch project.

              People

              • Assignee:
                jglick Jesse Glick
                Reporter:
                nkay101 Neil Kay
              • Votes:
                3 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: