The gerrit-code-review plugin always uses the most specific Jenkinsfile when discovering new changes, so that if a change *adds or *modifies* a Jenkinksfile, then it will use that to execute the pipeline.
This might be an unwanted behaviour, as the pipeline will just executed unreviewed/unmerged/unwanted code, which potentially could be faulty or (un)intentionally computationally expensive.

This change is about adding a new feature to allow the pipeline definition to decide whether to consider or ignore open changes that modify the Jenkinsfile executed by the pipeline.