For non pipeline jobs the plugin is configured in the jenkins main config and this config is automatically used in all jobs. This is quite fine, because there is nothing to do in the jobs which may be several 100 and more.

      But for pipeline jobs it is required to use an explicit "logFileFilter { ... }" in every Jenkinsfile. And for more complex Jenkinsfiles even serveral logFileFilter calls may be required.

      So it would be great to get a solution where the plugin is also automatically applied to all Pipeline jobs. Or at least it could be activated via "environment" or "options" tag.

       

          [JENKINS-67667] Make pipeline usage less explicit

          There are no comments yet on this issue.

            carlescapdevila Carles Capdevila
            milkyman Horst Krause
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: