[JIRA] (JENKINS-13655) Gzipped log are not shown correctly

2013-01-03 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-13655


Gzipped log are not shown correctly















Code changed in jenkins
User: Jesse Glick
Path:
 core/src/main/java/hudson/console/AnnotatedLargeText.java
 core/src/main/java/hudson/model/Run.java
 core/src/main/resources/hudson/model/Run/console.jelly
http://jenkins-ci.org/commit/jenkins/db8c92f736de3222ad0f1638f3893ca270bf877c
Log:
  Merge pull request #586 from HedAurabesh/v1.485_gzip

FIXED JENKINS-13655 Enable transparent log decompression support (Jenkins v1.485)


Compare: https://github.com/jenkinsci/jenkins/compare/35e1602ed148...db8c92f736de




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-13655) Gzipped log are not shown correctly

2013-01-03 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-13655


Gzipped log are not shown correctly















Code changed in jenkins
User: Martin Schroeder
Path:
 core/src/main/java/hudson/console/AnnotatedLargeText.java
 core/src/main/java/hudson/model/Run.java
 core/src/main/resources/hudson/model/Run/console.jelly
http://jenkins-ci.org/commit/jenkins/346fc998b16f2021cbd6b3bb1cd1878a2b19ff5b
Log:
  Enabled transparent compression support.

This only works if the "transparent GZIP support" patch has been
applied against Stapler. Otherwise, this patch will not compile
as the new "LargeText" constructor will not be found.

Additionally, the console.jelly was modified to make use of the
stream instead of the raw file, which is necessary to get the
correct uncompressed size of the file for skipping bytes.

JENKINS-2551
JENKINS-10400
JENKINS-13655

Signed-off-by: Martin Schroeder martin.h.schroe...@intel.com





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-13655) Gzipped log are not shown correctly

2013-01-03 Thread scm_issue_l...@java.net (JIRA)















































SCM/JIRA link daemon
 resolved  JENKINS-13655 as Fixed


Gzipped log are not shown correctly
















Change By:


SCM/JIRA link daemon
(03/Jan/13 10:21 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-13655) Gzipped log are not shown correctly

2013-01-03 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-13655


Gzipped log are not shown correctly















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
http://jenkins-ci.org/commit/jenkins/310e22dbfc0ef8753066f3059bd7cc82e80605b5
Log:
  JENKINS-13655 Noting.































This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-13655) Gzipped log are not shown correctly

2013-01-03 Thread dogf...@java.net (JIRA)














































dogfood
 commented on  JENKINS-13655


Gzipped log are not shown correctly















Integrated in  jenkins_main_trunk #2172
 JENKINS-13655 Noting. (Revision 310e22dbfc0ef8753066f3059bd7cc82e80605b5)

 Result = SUCCESS
Jesse Glick : 310e22dbfc0ef8753066f3059bd7cc82e80605b5
Files : 

	changelog.html





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-13655) Gzipped log are not shown correctly

2012-09-27 Thread lionh...@onlinehome.de (JIRA)














































Martin Schröder
 commented on  JENKINS-13655


Gzipped log are not shown correctly















Hello everyone.

This issue will be fixed as soon as the following pull request is merged into the Jenkins mainline:

https://github.com/jenkinsci/jenkins/pull/549

The only prerequisite is that Jenkins needs to be compiled against Stapler with a version = 1.196, as that includes this Stapler patchset:

https://github.com/stapler/stapler/pull/10




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-13655) Gzipped log are not shown correctly

2012-05-02 Thread dma...@gmail.com (JIRA)
dmatag created JENKINS-13655:


 Summary: Gzipped log are not shown correctly
 Key: JENKINS-13655
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13655
 Project: Jenkins
  Issue Type: Bug
  Components: log-parser, logaction
Affects Versions: current
 Environment: Linux, Jenkins 1.449, plugin timestamper 1.2.2
Reporter: dmatag
Assignee: rgoren
Priority: Minor


Gzipped logs are not currently shown. 

When de log file is gzip, log console shows 
 [8mha:kh+LCABb85aBtbiIQSajNKU4P08vOT+vOD8nVc 
+jsiC1KCczL9svvyT1dMUiOWdZ/mImBiZPBrac1Lz0kgwfBubSopwSBiGfrMSyRP2cxLx0/ 
eCSosy8dOuKIgYpNOOcITTIMAYIYGRiYKgoADJ4gGbolxanFuknJyelpJal5pTk5+cAAKxNYUeX 
 [0mccbdeveltool 
Building on master in workspace 

instead of 
Started by user ccbdeveltool 
Building on master in workspace 

These were issues in old Hudson: 
http://issues.hudson-ci.org/browse/HUDSON-2551 
http://issues.hudson-ci.org/browse/HUDSON-2137 



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira