[JIRA] (JENKINS-41845) Suppress default pipeline output

1 view
Skip to first unread message

cbanbery@aol.com (JIRA)

unread,
Feb 8, 2017, 9:37:01 AM2/8/17
to jenkinsc...@googlegroups.com
Callum Banbery created an issue
 
Jenkins / Improvement JENKINS-41845
Suppress default pipeline output
Issue Type: Improvement Improvement
Assignee: Unassigned
Components: pipeline
Created: 2017/Feb/08 2:36 PM
Environment: CloudBees Jenkins Enterprise 2.7.19.0.1
Labels: pipeline
Priority: Trivial Trivial
Reporter: Callum Banbery

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 is add too much information to our output. Ideally this should read:

Running on Agent1 in C:\Jenkins\workspace\TEST JOB

[TEST JOB] Running batch script
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

cbanbery@aol.com (JIRA)

unread,
Feb 8, 2017, 9:38:01 AM2/8/17
to jenkinsc...@googlegroups.com
Callum Banbery updated an issue
Change By: Callum Banbery
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 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}

andrew.bayer@gmail.com (JIRA)

unread,
Feb 10, 2017, 2:28:05 PM2/10/17
to jenkinsc...@googlegroups.com
Andrew Bayer updated an issue
Change By: Andrew Bayer
Component/s: workflow-step-api-plugin
Component/s: pipeline

scm_issue_link@java.net (JIRA)

unread,
Apr 6, 2018, 5:10:02 PM4/6/18
to jenkinsc...@googlegroups.com
SCM/JIRA link daemon commented on Improvement JENKINS-41845
 
Re: Suppress default pipeline output

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
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

svanoort@cloudbees.com (JIRA)

unread,
Apr 8, 2018, 10:27:02 AM4/8/18
to jenkinsc...@googlegroups.com
Sam Van Oort resolved as Fixed
 

Resolved as of 2.18 by supporting use of the Simple Theme Plugin to hide these (they now include the pipeline-annotated class).
Change By: Sam Van Oort
Status: Open Resolved
Resolution: Fixed

svanoort@cloudbees.com (JIRA)

unread,
Apr 8, 2018, 10:28:02 AM4/8/18
to jenkinsc...@googlegroups.com

Implementation to add the HTML class.

sverre.moe@gmail.com (JIRA)

unread,
Apr 11, 2018, 3:09:03 AM4/11/18
to jenkinsc...@googlegroups.com

Examples for using the CSS class pipeline-annotated would be nice.

.pipeline-annotated {

}

pino.silvaggio@gmail.com (JIRA)

unread,
Jul 23, 2018, 10:19:02 PM7/23/18
to jenkinsc...@googlegroups.com

I believe this works.

.pipeline-annotated {
    display: none;
}
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

aimeri@baddouh.me (JIRA)

unread,
Nov 13, 2018, 9:12:01 AM11/13/18
to jenkinsc...@googlegroups.com

For me what worked was:

 
.pipeline-new-node

{ display: none; }
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

aimeri@baddouh.me (JIRA)

unread,
Nov 13, 2018, 9:13:02 AM11/13/18
to jenkinsc...@googlegroups.com
Aimeri Baddouh edited a comment on Improvement JENKINS-41845
For me what worked was:

 
{code:java}
 .pipeline-new-node {
    display: none;
}
{code }

jglick@cloudbees.com (JIRA)

unread,
Nov 13, 2018, 9:46:03 AM11/13/18
to jenkinsc...@googlegroups.com
Jesse Glick reopened an issue
 

Yes the CSS was completely changed recently (see JENKINS-38381). Note however that if you hide the pipeline-new-node lines, you also lose the ability to collapse sections with the hide links. It ought to be possible to enhance NewNodeConsoleNote/script.js to have an option to hide all of these lines from the GUI, and recoverably.
Change By: Jesse Glick
Resolution: Fixed
Status: Resolved Reopened

r.fuereder@xortex.com (JIRA)

unread,
Nov 22, 2018, 7:29:02 AM11/22/18
to jenkinsc...@googlegroups.com

Jesse Glick Can it be that this ability to collapse sections with "(hide)" links is actually broken? Please note that I have not even known that something like this exists, so either I have never noticed that because I am blind, or are these links (that only appear via mouse over) actually new? (I just updated Jenkins plugins – and having a lot of guts – including "workflow-job:2.29")

jglick@cloudbees.com (JIRA)

unread,
Nov 27, 2018, 9:16:02 AM11/27/18
to jenkinsc...@googlegroups.com

Reinhold Füreder the (hide) links were introduced in workflow-job 2.26.

r.fuereder@xortex.com (JIRA)

unread,
Nov 27, 2018, 10:27:04 AM11/27/18
to jenkinsc...@googlegroups.com

Thanks Jesse Glick – that explains my confusion/semi-blindness very well

And since updating workflow-job plugin is still not recommended according to plugin center, I guess there is no sense in filing an issue for that, as the corresponding developers like Devin Nusbaum may be very well aware of it anyhow... ^^

Sorry for the fuss

jglick@cloudbees.com (JIRA)

unread,
Nov 27, 2018, 10:34:02 AM11/27/18
to jenkinsc...@googlegroups.com

I am the developer of this feature. If you are aware of some issues with it, please file in this component and assign to me, with steps to reproduce from scratch if possible.

r.fuereder@xortex.com (JIRA)

unread,
Nov 28, 2018, 3:00:04 AM11/28/18
to jenkinsc...@googlegroups.com

OK => I dared to file JENKINS-54904

ravi.v8@gmail.com (JIRA)

unread,
Jul 30, 2019, 2:43:07 PM7/30/19
to jenkinsc...@googlegroups.com

I use scripted pipelines heavily and I think the ability to toggle these lines as an option is really useful, removing a lot of clutter from logs and improving productivity.

Its nearly impossible to click hide of hundreds of blocks I have in large pipelines and also Blueocean's declarative pipelines is not an option as its not meant for advanced/ complex pipelines and is only for pipeline rookies (simpler, application oriented use-cases)

Jesse Glick I am an experienced used of scripted pipelines but new to plugin development, let me know how I can help and I'll be happy to spend time on this

ravi.v8@gmail.com (JIRA)

unread,
Jul 30, 2019, 2:43:08 PM7/30/19
to jenkinsc...@googlegroups.com
Ravi Godavarthi edited a comment on Improvement JENKINS-41845
I use scripted pipelines heavily and I think the ability to toggle these lines as an option is really useful, removing a lot of clutter from logs and improving productivity.

Its nearly impossible to click hide of hundreds of blocks I have in large pipelines and also Blueocean's declarative pipelines is not an option as its not meant for advanced/ complex pipelines and is only for pipeline rookies (simpler, application oriented use-cases)

[~jglick] I am an experienced used user of scripted pipelines but new to plugin development, let me know how I can help and I'll be happy to spend time on this

jglick@cloudbees.com (JIRA)

unread,
Jul 31, 2019, 2:11:04 PM7/31/19
to jenkinsc...@googlegroups.com

Ravi Godavarthi this has little or nothing to do with Scripted vs. Declarative Pipeline syntax. You can use either the “classic” or Blue Ocean UIs to display execution results. (B.O. does impose certain restrictions on the structure of flow graphs which it is able to display; Declarative syntax is designed to only produce graphs which follow those restrictions, though you can do the same from Scripted syntax with a bit of care.)

At any rate,

removing a lot of clutter from logs

is a valid goal.

new to plugin development, let me know how I can help

This would be a patch to workflow-job-plugin, probably tested only interactively (mvn hpi:run) since I do not know of a straightforward way to automate it. I would try patching src/main/resources/org/jenkinsci/plugins/workflow/job/console/NewNodeConsoleNote/script.js to offer some sort of button to toggle display of pipeline-new-node spans, ideally persisting this preference in the browser. (It could also be stored in a UserProperty but that would require some more complicated Java plumbing I do not want to go into right now.)

dar.amit@gmail.com (JIRA)

unread,
Dec 12, 2019, 9:04:03 AM12/12/19
to jenkinsc...@googlegroups.com
Amit Dar commented on Improvement JENKINS-41845

after adding both:

 {{.pipeline-annotated {
display: none;
}}}

and:

 {{.pipeline-new-node {
    display: none;
}}}

I'm still seeing the lines that originally had the pipeline output, but now they only show the time and line number (other plugins I'm using).

 

here:
15:36:20 Started by user Dar Amit

http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L215:36:20 Running in Durability level: PERFORMANCE_OPTIMIZED

http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L315:36:22 

http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L415:36:22 

http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L515:36:22 

http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L615:36:22 

http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L715:36:22 

http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L815:36:22 

http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L915:36:22 

http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L1015:36:22 

http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L1115:36:22 

http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L1215:36:22 test first stage

http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L1315:36:22 

http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L1415:36:22 

http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L1515:36:22 test second stage

http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L1615:36:22 

http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L1715:36:22 

http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L1815:36:22

 

when view the console as plain text, I see:

[2019-12-12T13:36:20.913Z] Started by user Dar Amit
[2019-12-12T13:36:20.988Z] Running in Durability level: PERFORMANCE_OPTIMIZED
[2019-12-12T13:36:22.129Z] [Pipeline] Start of Pipeline
[2019-12-12T13:36:22.530Z] [Pipeline] parallel
[2019-12-12T13:36:22.578Z] [Pipeline] { (Branch: firstBranch)
[2019-12-12T13:36:22.583Z] [Pipeline] { (Branch: secondBranch)
[2019-12-12T13:36:22.629Z] [Pipeline] stage
[2019-12-12T13:36:22.664Z] [Pipeline] { (first)
[2019-12-12T13:36:22.666Z] [Pipeline] stage
[2019-12-12T13:36:22.670Z] [Pipeline]

{ (second) [2019-12-12T13:36:22.684Z] [Pipeline] echo [2019-12-12T13:36:22.685Z] test first stage [2019-12-12T13:36:22.686Z] [Pipeline] }

[2019-12-12T13:36:22.694Z] [Pipeline] echo
[2019-12-12T13:36:22.694Z] test second stage
[2019-12-12T13:36:22.702Z] [Pipeline] }

 

Am I missing something here? I thought the whole idea was to remove those lines completely...

{{}}
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

dar.amit@gmail.com (JIRA)

unread,
Dec 12, 2019, 9:05:04 AM12/12/19
to jenkinsc...@googlegroups.com
Amit Dar edited a comment on Improvement JENKINS-41845
Using: Jenkins 2.190.2,

Simple Theme plugin 0.5.1

 

 after adding both the following as extra css in simple theme plugin :

 {{.pipeline-annotated \ {
    display: none;
}}}

{{and:}}

 {{.pipeline-new-node \ {

    display: none;
}}}

I'm still seeing the lines that originally had the pipeline output, but now they only show the time and line number (other plugins I'm using).

 

here:
*15:36:20* Started by user [Dar Amit|http://eltivxejenkins:31780/user/ad72201]

[ | http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L2]*15:36:20* Running in Durability level: PERFORMANCE_OPTIMIZED

[ | http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L3]*15:36:22* 

[ | http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L4]*15:36:22* 

[ | http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L5]*15:36:22* 

[ | http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L6]*15:36:22* 

[ | http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L7]*15:36:22* 

[ | http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L8]*15:36:22* 

[ | http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L9]*15:36:22* 

[ | http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L10]*15:36:22* 

[ | http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L11]*15:36:22* 

[ | http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L12]*15:36:22* test first stage

[ | http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L13]*15:36:22* 

[ | http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L14]*15:36:22* 

[ | http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L15]*15:36:22* test second stage

[ | http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L16]*15:36:22* 

[ | http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L17]*15:36:22* 

[ | http://eltivxejenkins:31780/job/piepline%20groovy/2/console#L18]*15:36:22*


 

when view the console as plain text, I see:

[2019-12-12T13:36:20.913Z] Started by user Dar Amit
[2019-12-12T13:36:20.988Z] Running in Durability level: PERFORMANCE_OPTIMIZED
[2019-12-12T13:36:22.129Z] [Pipeline] Start of Pipeline
[2019-12-12T13:36:22.530Z] [Pipeline] parallel
[2019-12-12T13:36:22.578Z] [Pipeline] { (Branch: firstBranch)
[2019-12-12T13:36:22.583Z] [Pipeline] { (Branch: secondBranch)
[2019-12-12T13:36:22.629Z] [Pipeline] stage
[2019-12-12T13:36:22.664Z] [Pipeline] { (first)
[2019-12-12T13:36:22.666Z] [Pipeline] stage
[2019-12-12T13:36:22.670Z] [Pipeline]
{ (second)
[2019-12-12T13:36:22.684Z] [Pipeline] echo
[2019-12-12T13:36:22.685Z] test first stage
[2019-12-12T13:36:22.686Z] [Pipeline] }
[2019-12-12T13:36:22.694Z] [Pipeline] echo
[2019-12-12T13:36:22.694Z] test second stage
[2019-12-12T13:36:22.702Z] [Pipeline] }

 

Am I missing something here? I thought the whole idea was to remove those lines completely...

{{}}

dar.amit@gmail.com (JIRA)

unread,
Dec 12, 2019, 9:28:03 AM12/12/19
to jenkinsc...@googlegroups.com
Amit Dar edited a comment on Improvement JENKINS-41845
Using: Jenkins 2.190.2,

Simple Theme plugin 0.5.1

 

after adding the following as extra css in simple theme plugin:

 {{.pipeline-annotated {

{ display: none; }

}} }

{{and:}}

 {{.pipeline-new-node {

{     display: none; }

}} }

I'm still seeing the lines that originally had the pipeline output, but now they only show the time and line number (other plugins I'm using).

 

here:
*15: 36 46 : 20 34 * Started by user [Dar Amit|http://eltivxejenkins:31780/user/ad72201]

[ | http://eltivxejenkins:31780/job/piepline%20groovy/ 2 6 /console#L2]*15: 36 46 : 20 34 * Running in Durability level: PERFORMANCE_OPTIMIZED

[ | http://eltivxejenkins:31780/job/piepline%20groovy/ 2 6 /console#L3]*15: 36 46 : 22 34 * 

[ | http://eltivxejenkins:31780/job/piepline%20groovy/ 2 6 /console#L4]*15: 36 46 : 22 34 * 

[ | http://eltivxejenkins:31780/job/piepline%20groovy/ 2 6 /console#L5]*15: 36 46 : 22 34 * 

[ | http://eltivxejenkins:31780/job/piepline%20groovy/ 2 6 /console#L6]*15: 36 46 : 22 34 * 

[ | http://eltivxejenkins:31780/job/piepline%20groovy/ 2 6 /console#L7]*15: 36 46 : 22 34 * 

[ | http://eltivxejenkins:31780/job/piepline%20groovy/ 2 6 /console#L8]*15: 36 46 : 22 34 * 

[ | http://eltivxejenkins:31780/job/piepline%20groovy/ 2 6 /console#L9]*15: 36 46 : 22 34 * 

[ | http://eltivxejenkins:31780/job/piepline%20groovy/ 2 6 /console#L10]*15: 36 46 : 22 34 * 

[ | http://eltivxejenkins:31780/job/piepline%20groovy/ 2 6 /console#L11]*15: 36 46 : 22 34 * 

[ | http://eltivxejenkins:31780/job/piepline%20groovy/ 2 6 /console#L12]*15: 36 46 : 22 34 * test first stage

[ | http://eltivxejenkins:31780/job/piepline%20groovy/ 2 6 /console#L13]*15: 36 46 : 22 34 * 

[ | http://eltivxejenkins:31780/job/piepline%20groovy/ 2 6 /console#L14]*15: 36 46 : 22 34 * 

[ | http://eltivxejenkins:31780/job/piepline%20groovy/ 2 6 /console#L15]*15: 36 46 : 22 34 * test second stage

[ | http://eltivxejenkins:31780/job/piepline%20groovy/ 2 6 /console#L16]*15: 36 46 : 22 34 * 

[ | http://eltivxejenkins:31780/job/piepline%20groovy/ 2 6 /console#L17]*15: 36 46 : 22 34 * 

[ | http://eltivxejenkins:31780/job/piepline%20groovy/ 2 6 /console#L18]*15: 36 46 : 22 34 *

 

 ** when view the console as plain text, I see:


[2019-12-12T13:36:20.913Z] Started by user Dar Amit
[2019-12-12T13:36:20.988Z] Running in Durability level: PERFORMANCE_OPTIMIZED
[2019-12-12T13:36:22.129Z] [Pipeline] Start of Pipeline
[2019-12-12T13:36:22.530Z] [Pipeline] parallel
[2019-12-12T13:36:22.578Z] [Pipeline] { (Branch: firstBranch)
[2019-12-12T13:36:22.583Z] [Pipeline] { (Branch: secondBranch)
[2019-12-12T13:36:22.629Z] [Pipeline] stage
[2019-12-12T13:36:22.664Z] [Pipeline] { (first)
[2019-12-12T13:36:22.666Z] [Pipeline] stage
[2019-12-12T13:36:22.670Z] [Pipeline]

{ (second) [2019-12-12T13:36:22.684Z] [Pipeline] echo [2019-12-12T13:36:22.685Z] test first stage [2019-12-12T13:36:22.686Z] [Pipeline] }

[2019-12-12T13:36:22.694Z] [Pipeline] echo
[2019-12-12T13:36:22.694Z] test second stage
[2019-12-12T13:36:22.702Z] [Pipeline] }

 

Am I missing something here? I thought the whole idea was to remove those lines completely...

{{}}

dar.amit@gmail.com (JIRA)

unread,
Dec 12, 2019, 9:29:04 AM12/12/19
to jenkinsc...@googlegroups.com
Amit Dar edited a comment on Improvement JENKINS-41845
Using: Jenkins 2.190.2,

Simple Theme plugin 0.5.1

 

after adding the following as extra css in simple theme plugin:

 {{.pipeline-annotated

{ display: none; }

}}

{{and:}}

 {{.pipeline-new-node

{     display: none; }

}}

I'm still seeing the lines that originally had the pipeline output, but now they only show the time and line number (other plugins I'm using).

  

 here:
 *
15:46:34 *  Started by user  [ Dar Amit |http://eltivxejenkins:31780/user/ad72201]

[|http://eltivxejenkins:31780/job/piepline%20groovy/6/console#L2]* 15:46:34 *  Running in Durability level: PERFORMANCE_OPTIMIZED
[|http://eltivxejenkins:31780/job/piepline%20groovy/6/console#L3]* 15:46:34 * 

[|http://eltivxejenkins:31780/job/piepline%20groovy/6/console#L4]*
15:46:34 * 

[|http://eltivxejenkins:31780/job/piepline%20groovy/6/console#L5]*
15:46:34 * 

[|http://eltivxejenkins:31780/job/piepline%20groovy/6/console#L6]*
15:46:34 * 

[|http://eltivxejenkins:31780/job/piepline%20groovy/6/console#L7]*
15:46:34 * 

[|http://eltivxejenkins:31780/job/piepline%20groovy/6/console#L8]*
15:46:34 * 

[|http://eltivxejenkins:31780/job/piepline%20groovy/6/console#L9]*
15:46:34 * 

[|http://eltivxejenkins:31780/job/piepline%20groovy/6/console#L10]*
15:46:34 * 

[|http://eltivxejenkins:31780/job/piepline%20groovy/6/console#L11]*
15:46:34 * 

[|http://eltivxejenkins:31780/job/piepline%20groovy/6/console#L12]*
15:46:34 *  test first stage
[|http://eltivxejenkins:31780/job/piepline%20groovy/6/console#L13]* 15:46:34 * 

[|http://eltivxejenkins:31780/job/piepline%20groovy/6/console#L14]*
15:46:34 * 

[|http://eltivxejenkins:31780/job/piepline%20groovy/6/console#L15]*
15:46:34 *  test second stage
[|http://eltivxejenkins:31780/job/piepline%20groovy/6/console#L16]* 15:46:34 * 

[|http://eltivxejenkins:31780/job/piepline%20groovy/6/console#L17]*
15:46:34 * 

[|http://eltivxejenkins:31780/job/piepline%20groovy/6/console#L18]*
15:46:34 *

 

 ** when I view the console as plain text, I see:


[2019-12-12T13:36:20.913Z] Started by user Dar Amit
[2019-12-12T13:36:20.988Z] Running in Durability level: PERFORMANCE_OPTIMIZED
[2019-12-12T13:36:22.129Z] [Pipeline] Start of Pipeline
[2019-12-12T13:36:22.530Z] [Pipeline] parallel
[2019-12-12T13:36:22.578Z] [Pipeline] { (Branch: firstBranch)
[2019-12-12T13:36:22.583Z] [Pipeline] { (Branch: secondBranch)
[2019-12-12T13:36:22.629Z] [Pipeline] stage
[2019-12-12T13:36:22.664Z] [Pipeline] { (first)
[2019-12-12T13:36:22.666Z] [Pipeline] stage
[2019-12-12T13:36:22.670Z] [Pipeline]

{ (second) [2019-12-12T13:36:22.684Z] [Pipeline] echo [2019-12-12T13:36:22.685Z] test first stage [2019-12-12T13:36:22.686Z] [Pipeline] }

[2019-12-12T13:36:22.694Z] [Pipeline] echo
[2019-12-12T13:36:22.694Z] test second stage
[2019-12-12T13:36:22.702Z] [Pipeline] }

 

Am I missing something here? I thought the whole idea was to remove those lines completely...

{{}}

dar.amit@gmail.com (JIRA)

unread,
Dec 12, 2019, 9:48:03 AM12/12/19
to jenkinsc...@googlegroups.com
Amit Dar edited a comment on Improvement JENKINS-41845
Using: Jenkins 2.190.2,

Simple Theme plugin 0.5.1
* timestamp are enabled for all pipeline jobs.
 

after adding the following as extra css in simple theme plugin:

 {{.pipeline-annotated

{ display: none; }

}}

{{and:}}

 {{.pipeline-new-node

{     display: none; }

}}

I'm still seeing the lines that originally had the pipeline output, but now they only show the time and line number (other plugins I'm using).

here:

15:46:34 Started by user Dar Amit
15:46:34 Running in Durability level: PERFORMANCE_OPTIMIZED
15:46:34
15:46:34
15:46:34
15:46:34
15:46:34
15:46:34
15:46:34
15:46:34
15:46:34
15:46:34 test first stage
15:46:34
15:46:34
15:46:34 test second stage
15:46:34
15:46:34
15:46:34


 

when I view the console as plain text, I see:

[2019-12-12T13:36:20.913Z] Started by user Dar Amit
[2019-12-12T13:36:20.988Z] Running in Durability level: PERFORMANCE_OPTIMIZED
[2019-12-12T13:36:22.129Z] [Pipeline] Start of Pipeline
[2019-12-12T13:36:22.530Z] [Pipeline] parallel
[2019-12-12T13:36:22.578Z] [Pipeline] { (Branch: firstBranch)
[2019-12-12T13:36:22.583Z] [Pipeline] { (Branch: secondBranch)
[2019-12-12T13:36:22.629Z] [Pipeline] stage
[2019-12-12T13:36:22.664Z] [Pipeline] { (first)
[2019-12-12T13:36:22.666Z] [Pipeline] stage
[2019-12-12T13:36:22.670Z] [Pipeline]

{ (second) [2019-12-12T13:36:22.684Z] [Pipeline] echo [2019-12-12T13:36:22.685Z] test first stage [2019-12-12T13:36:22.686Z] [Pipeline] }

[2019-12-12T13:36:22.694Z] [Pipeline] echo
[2019-12-12T13:36:22.694Z] test second stage
[2019-12-12T13:36:22.702Z] [Pipeline] }

 

Am I missing something here? I thought the whole idea was to remove those lines completely...

{{}}


UPDATE: removing the line number plugin and disable the timestamp in the jenkins configuration solved it, but still I would expect the line number and timestamp to show  in the displayed lines (without all the pipeline output clutter).

tonkasanders@gmail.com (JIRA)

unread,
Mar 10, 2020, 12:18:04 PM3/10/20
to jenkinsc...@googlegroups.com

I'm on Jenkins version 2.195, running in classic mode, and I added the following to the Simple Theme Plugin.

 

.pipeline-annotated {
     display: none; 
}
.pipeline-new-node {
      display: none; 
}

Works for me. The console is nice and clean.  Only seeing the output I want/need to.

 
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages