[JENKINS-49835] Do not trigger new build on Mercurial insignificant changes

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.

relates to

JENKINS-62669 Remove BitBucket Mercurial integration

Luis Piedra-Márquez created issue - 2018-03-02 08:24

Jesse Glick made changes - 2020-06-11 20:54

Link

New: This issue relates to ~~JENKINS-62669~~ [ ~~JENKINS-62669~~ ]

Kalle Niemitalo made changes - 2021-11-12 09:57

Link

New: This issue is related to ~~JENKINS-62669~~ [ ~~JENKINS-62669~~ ]

Kalle Niemitalo made changes - 2021-11-12 09:57

Resolution		New: Won't Do [ 10001 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Kalle Niemitalo made changes - 2021-11-12 09:58

Link

Original: This issue is related to ~~JENKINS-62669~~ [ ~~JENKINS-62669~~ ]

Jenkins