For all changes in the Puppet repository, the lint checks operations-puppet-puppetlint-lenient and puppetlint-strict are run.
Those fail all the time, thus a) they are being ignored for the most part and b) they require developers and reviewers who are interested in them to go to the details page and search for the names of the files that a change touched to see if (new) warnings were added.
The repository should be made compliant with the lint checks or, where those are too severe or, when importing external modules, comparability with upstream is more important than linting, they should be disabled for those cases either in the repository (preferred) or in the Jenkins job definition.