-
Improvement
-
Resolution: Unresolved
-
Trivial
-
None
-
CloudBees Jenkins Enterprise 2.7.19.0.1
Currently the pipeline plugin prints the steps into the console output, prefixed with [Pipeline]
[Pipeline] node
Running on Agent1 in C:\Jenkins\workspace\TEST JOB
[Pipeline] {
[Pipeline] withEnv
[Pipeline] {
[Pipeline] withCredentials
[Pipeline] {
[Pipeline] bat
[TEST JOB] Running batch script
[Pipeline] }
[Pipeline] // withCredentials
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
Is it possible to have a flag somewhere to disable this logging, either in the pipeline itself or configurable at a master level. I'd like to remove this extra logging as it adds too much information to our output. Ideally this should read:
Running on Agent1 in C:\Jenkins\workspace\TEST JOB [TEST JOB] Running batch script
- relates to
-
JENKINS-38381 [JEP-210] Optimize log handling in Pipeline and Durable Task
-
- Resolved
-
- links to
[JENKINS-41845] Suppress default pipeline output
Callum Banbery
created issue -
Callum Banbery
made changes -
| Description |
Original:
Currently the pipeline plugin prints the steps into the console output, prefixed with [Pipeline] {code:java} [Pipeline] node Running on Agent1 in C:\Jenkins\workspace\TEST JOB [Pipeline] { [Pipeline] withEnv [Pipeline] { [Pipeline] withCredentials [Pipeline] { [Pipeline] bat [TEST JOB] Running batch script [Pipeline] } [Pipeline] // withCredentials [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node {code} Is it possible to have a flag somewhere to disable this logging, either in the pipeline itself or configurable at a master level. I'd like to remove this extra logging as is add too much information to our output. Ideally this should read: {code:java} Running on Agent1 in C:\Jenkins\workspace\TEST JOB [TEST JOB] Running batch script {code} |
New:
Currently the pipeline plugin prints the steps into the console output, prefixed with [Pipeline] {code:java} [Pipeline] node Running on Agent1 in C:\Jenkins\workspace\TEST JOB [Pipeline] { [Pipeline] withEnv [Pipeline] { [Pipeline] withCredentials [Pipeline] { [Pipeline] bat [TEST JOB] Running batch script [Pipeline] } [Pipeline] // withCredentials [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node {code} Is it possible to have a flag somewhere to disable this logging, either in the pipeline itself or configurable at a master level. I'd like to remove this extra logging as it adds too much information to our output. Ideally this should read: {code:java} Running on Agent1 in C:\Jenkins\workspace\TEST JOB [TEST JOB] Running batch script {code} |
| Component/s | New: workflow-step-api-plugin [ 21718 ] | |
| Component/s | Original: pipeline [ 21692 ] |
| Component/s | New: workflow-job-plugin [ 21716 ] | |
| Component/s | Original: workflow-step-api-plugin [ 21718 ] | |
| Labels | Original: pipeline |
Code changed in jenkins
User: Marc MacIntyre
Path:
src/main/java/org/jenkinsci/plugins/workflow/job/console/WorkflowRunConsoleNote.java
http://jenkins-ci.org/commit/workflow-job-plugin/d0e19f62c377bbcace954176f65297b958c08dc6
Log:
Add the CSS class "pipeline-annotated" to all pipeline annotated console messages. This will allow the administrator to override the display of these messages using the Simple Theme Plugin.
This should fix JENKINS-41845
Sam Van Oort
added a comment - Resolved as of 2.18 by supporting use of the Simple Theme Plugin to hide these (they now include the pipeline-annotated class).
Sam Van Oort
added a comment - Resolved as of 2.18 by supporting use of the Simple Theme Plugin to hide these (they now include the pipeline-annotated class). Sam Van Oort
made changes -
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Sam Van Oort
added a comment - Implementation to add the HTML class. Sam Van Oort
made changes -
| Remote Link | New: This issue links to "Workflow-job #90 (Web Link)" [ 20392 ] |
Please file issues under the component pipeline if you do not actually know the plugin implementing a given aspect of behavior.