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

Do not trigger new build on Mercurial insignificant changes

    XMLWordPrintable

Details

    Description

      In Mercurial, a new tag means a new commit to the repository.

      Mercurial plugin has some code to ignore insignificant changes when polling repository:

      if (depchanges.isEmpty()) {
      
          output.println(Messages.MercurialSCM_non_dependent_changes_detected());
      
          return Change.INSIGNIFICANT;
      
      }

      But this is behavior is not available when using it in multibranch pipelines.

      It should be configurable, since many people could be using this behavior to detect new tags and thus triggering deployments.

       

       

      Attachments

        Issue Links

          Activity

            jglick Jesse Glick added a comment -

            Candidate for closing: JENKINS-62669

            jglick Jesse Glick added a comment - Candidate for closing: JENKINS-62669

            This change would no longer be useful. Mercurial support was removed from the plugin in JENKINS-62669 because Bitbucket Cloud no longer supports Mercurial and Bitbucket Server never did.

            kon Kalle Niemitalo added a comment - This change would no longer be useful. Mercurial support was removed from the plugin in JENKINS-62669 because Bitbucket Cloud no longer supports Mercurial and Bitbucket Server never did.

            People

              Unassigned Unassigned
              luispiedra Luis Piedra-Márquez
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: