[JIRA] (JENKINS-54678) Compression trick not supported by JEP-210

2 views
Skip to first unread message

jglick@cloudbees.com (JIRA)

unread,
Nov 30, 2018, 11:24:04 AM11/30/18
to jenkinsc...@googlegroups.com
Jesse Glick updated an issue
 
Jenkins / Bug JENKINS-54678
Compression trick not supported by JEP-210
Change By: Jesse Glick
Summary: Logs are lost in Multibranch Pipleline after the build has finished Compression trick not supported by JEP-210
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

jglick@cloudbees.com (JIRA)

unread,
Nov 30, 2018, 11:27:02 AM11/30/18
to jenkinsc...@googlegroups.com
Jesse Glick commented on Bug JENKINS-54678
 
Re: Compression trick not supported by JEP-210

I think there was some environment variable to limit the the log size. Where can I find it?

I am not aware of any such variable, and cannot guess what it would do.

is the plugin logfilesizechecker safe to use?

That is using Run.getLogText so it ought to work. (I have not tried.)

How can i override MAX_LINES_READ in Jenkinsfile?

I do not know what that variable is or what you think it should be doing. Probably unrelated to this issue—should be asked on the users’ list etc.

rick.d.vries@gmail.com (JIRA)

unread,
Apr 2, 2019, 5:05:02 AM4/2/19
to jenkinsc...@googlegroups.com

rick.d.vries@gmail.com (JIRA)

unread,
Apr 2, 2019, 5:06:03 AM4/2/19
to jenkinsc...@googlegroups.com
Rick de Vries assigned an issue to Unassigned

rick.d.vries@gmail.com (JIRA)

unread,
Apr 2, 2019, 5:07:01 AM4/2/19
to jenkinsc...@googlegroups.com
Rick de Vries commented on Bug JENKINS-54678
 
Re: Compression trick not supported by JEP-210

Renaming the log.gz to log also makes it possible for jenkins to render the log.

rick.d.vries@gmail.com (JIRA)

unread,
Apr 2, 2019, 5:09:02 AM4/2/19
to jenkinsc...@googlegroups.com
Rick de Vries edited a comment on Bug JENKINS-54678
Renaming the ' log.gz ' to ' log ' also makes it possible for jenkins to render the log.


This way you dont have to unzip the log (which saves diskspace)

 

rick.d.vries@gmail.com (JIRA)

unread,
May 15, 2019, 2:55:02 AM5/15/19
to jenkinsc...@googlegroups.com

Any ETA on when this is going to be fixed?

isarkisov@gmail.com (JIRA)

unread,
Aug 13, 2019, 3:11:03 PM8/13/19
to jenkinsc...@googlegroups.com

What's the solution here, is it as simple as having compressed log stored as log vs log.gz?

jglick@cloudbees.com (JIRA)

unread,
Aug 13, 2019, 9:34:04 PM8/13/19
to jenkinsc...@googlegroups.com

rgerasch@gmx.de (JIRA)

unread,
Oct 7, 2019, 9:43:03 AM10/7/19
to jenkinsc...@googlegroups.com

if resulting file log.gz is renamed to log jenkins is able to show the log content.

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

akostadinov@java.net (JIRA)

unread,
Apr 15, 2020, 9:45:08 AM4/15/20
to jenkinsc...@googlegroups.com

Yeah, I can confirm that keeping the file name `log` even though it is compressed, keeps things working.

Can't it just create a symlink log -> log.gz ?

Jesse Glick, any plan to fix it?

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

jglick@cloudbees.com (JIRA)

unread,
Apr 15, 2020, 10:32:06 AM4/15/20
to jenkinsc...@googlegroups.com

Jesse Glick, any plan to fix it?

Me? No, I do not work on this plugin. If it has a maintainer, it would be up to them.

franrobles1@hotmail.com (JIRA)

unread,
Apr 15, 2020, 10:50:15 AM4/15/20
to jenkinsc...@googlegroups.com

akostadinov the plugin is marked as "up for adoption": https://plugins.jenkins.io/compress-buildlog/

Looks like its main developer (also some tickets here in Jira are still assigned to him) was Daniel Beck. He could maybe give some light there.

dbeck@cloudbees.com (JIRA)

unread,
Apr 15, 2020, 11:19:09 AM4/15/20
to jenkinsc...@googlegroups.com

I plan to release https://github.com/jenkinsci/compress-buildlog-plugin/pull/10 soon, which just drops Pipeline support. I am not currently interested in implementing support for it, and that way the plugin at least works for other use cases.

Reply all
Reply to author
Forward
0 new messages