[JIRA] [ansicolor] (JENKINS-11752) ANSI color plugin adds garbage to log

2013-04-29 Thread anze.za...@cosylab.com (JIRA) 














































Anze Zagar
 commented on  JENKINS-11752


ANSI color plugin adds garbage to log















Suggested temporary fix (until JENKINS-13816 allows better way of doing this):

 src/main/java/hudson/plugins/ansicolor/AnsiColorNote.java	(revision 36259)
+++ src/main/java/hudson/plugins/ansicolor/AnsiColorNote.java	(working copy)
@@ -65,6 +65,7 @@
 	 */
 @Override
 public ConsoleAnnotator annotate(Object context, MarkupText text, int charPos) {
+	if (this.data.contains(ConsoleNote.PREAMBLE_STR)) return null;
 try {
 	String colorizedData = colorize(StringEscapeUtils.escapeHtml(this.data), this.getColorMap());
 	if (! colorizedData.contentEquals(this.data)) {



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-15329) build.xml no longer optimizing upstreamCauses element using references

2012-09-27 Thread anze.za...@cosylab.com (JIRA) 














































Anze Zagar
 created  JENKINS-15329


build.xml no longer optimizing upstreamCauses element using references















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


core



Created:


27/Sep/12 8:55 AM



Description:


Jobs built after being triggered by a large chain of upstream jobs produce tremendous build.xml and log files.

For example, previously (in past Jenkins versions, not sure which but it must have been from like 3 months ago that I last built such a chain of jobs) build.xml's causes element consisted of elements like this:

hudson.model.Cause_-UpstreamCause
  upstreamProjectproject2/upstreamProject
  upstreamUrljob/project2//upstreamUrl
  upstreamBuild5/upstreamBuild
  upstreamCauses
hudson.model.Cause_-UpstreamCause
  upstreamProjectproject1/upstreamProject
  upstreamUrljob/project1//upstreamUrl
  upstreamBuild3/upstreamBuild
  upstreamCauses
hudson.model.Cause_-UpstreamCause reference="../../../../../hudson.model.Cause_-UpstreamCause2/upstreamCauses/hudson.model.Cause_-UpstreamCause"/
  /upstreamCauses
/hudson.model.Cause_-UpstreamCause
  /upstreamCauses
/hudson.model.Cause_-UpstreamCause

The upstream cause which is already listed previously in the build.xml is simply just referenced so the whole tree of upstream causes doesn't need to repeat.

But now instead of having the hudson.model.Cause_-UpstreamCause reference..., build.xml contains completely dereferenced chanin of upstream causes. This of course doesn't scale because build.xml files will grow exponentally with the size of the job dependency chain. The same problem is also with the console log files.

Efectivelly, I now have jobs which were triggered by a chain of nearly 100 other jobs and which have build.xml and console log files of sizes of several GBs (just for one build of one job!?). This of course also crashes Jenkins on startup when it wants to load these files.




Project:


Jenkins



Priority:


Major



Reporter:


Anze Zagar

























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