[JIRA] (JENKINS-61110) Need a new option for BUILD_LOG macro to truncate a tail

11 views
Skip to first unread message

haridara@gmail.com (JIRA)

unread,
Feb 17, 2020, 5:57:05 AM2/17/20
to jenkinsc...@googlegroups.com
Hari Dara created an issue
 
Jenkins / Improvement JENKINS-61110
Need a new option for BUILD_LOG macro to truncate a tail
Issue Type: Improvement Improvement
Assignee: Alex Earl
Components: token-macro-plugin
Created: 2020-02-17 10:56
Priority: Minor Minor
Reporter: Hari Dara

When generating an email alert on a failure, I would like to highlight the failure message/exception all by itself in a separate section. If this error is already logged to console, it tends to repeat when including the tail of the console log using BUILD_LOG macro and reduce the readability of the email (I prefer crisp and concise emails). I can avoid this duplication if there is support for an additional parameter to drop the specified number of lines from the tail. This is also useful to remove boilerplate messages that always exist at the end of a build.

 

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

haridara@gmail.com (JIRA)

unread,
Feb 17, 2020, 5:58:02 AM2/17/20
to jenkinsc...@googlegroups.com
Hari Dara assigned an issue to Hari Dara
Change By: Hari Dara
Assignee: Alex Earl Hari Dara

haridara@gmail.com (JIRA)

unread,
Feb 17, 2020, 6:00:02 AM2/17/20
to jenkinsc...@googlegroups.com

haridara@gmail.com (JIRA)

unread,
Feb 17, 2020, 6:00:02 AM2/17/20
to jenkinsc...@googlegroups.com

haridara@gmail.com (JIRA)

unread,
Feb 17, 2020, 6:00:03 AM2/17/20
to jenkinsc...@googlegroups.com
Hari Dara started work on Improvement JENKINS-61110
 
Change By: Hari Dara
Status: Open In Progress

haridara@gmail.com (JIRA)

unread,
Feb 18, 2020, 12:34:03 PM2/18/20
to jenkinsc...@googlegroups.com
Change By: Hari Dara
Status: In Review Fixed but Unreleased
Resolution: Fixed

haridara@gmail.com (JIRA)

unread,
Feb 19, 2020, 4:55:02 AM2/19/20
to jenkinsc...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages