Selective CI builds

[Shpinkso]

As a product owner
I want documentation changes to go straight to review without CI build/tests
so that CI resources are not used needlessly and documentation changes can happen more efficiently

Acceptance criteria:

• Some defined list of files or file extension types representing non-functional documentation do not trigger a CI build at PR

[nikhil-zinjurde-imgtec]

One option could be to ignore commits with certain messages i.e. if the commits include certain words, they can be ignored from triggering a CI build

checkout([$class: 'GitSCM',
    extensions: scm.extensions + [
        [$class: 'MessageExclusion', excludedMessage: '.*\\[ignore-this-commit\\].*']],
    ],
])

But, it seems there is currently a bug open in Jenkins that prevents the above option from working - https://issues.jenkins-ci.org/browse/JENKINS-36195

[Ham22]

Comments would allow devs to bypass the CI where as we want the CI to decide right? Filtering the trigger on files paths/names/types seems sensible. Filtering out the triggers may not be the best thing to do however because our process requires a CI pass to allow a merge. Perhaps best would be to just add some logic to the Jenkinsfile to do simpler builds/tests or just return success directly on certain file changes?

[nikhil-zinjurde-imgtec]

Better approach to take as put here and extend towards different patterns:
https://gist.github.com/lsjostro/3f410333ac90ecccfdc139079f585b3a