Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-5337

Huge logs if there is a problem initializing ivy based project

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • ivy-plugin
    • None
    • Linux

      I have edited the initial bug as i found out that the fix has been already released.

      Please, take a look at the excessive logging problem. As soon as there is a problem initializing ivy settings for the project it generates megabytes of repetitive logs seems because of many cycles, so a problem reading ivy.xml file for one project can generate up 30MB of log. Considering the fact the ivy plugin v 0.3 had a problem with remembering correct settings (supposed to be fixed in 0.4) we were sometimes ending up with 100-300 MB of logs to analyze which projects are corrupted.

          [JENKINS-5337] Huge logs if there is a problem initializing ivy based project

          Is this still a problem with the latest version of the Ivy plugin?

          Timothy Bingaman added a comment - Is this still a problem with the latest version of the Ivy plugin?

          eguess74 added a comment -

          I tried to run Hudson 1.339 with ivy plugin 0.6 - it failed to start with ClassNotFound exception complaining about some inner class of hudson/model/DependencyGraph

          cannot provide logs for that error, but i guess it should be easily reproducible... should i update to hudson 1.341 in order for plugin to work?

          eguess74 added a comment - I tried to run Hudson 1.339 with ivy plugin 0.6 - it failed to start with ClassNotFound exception complaining about some inner class of hudson/model/DependencyGraph cannot provide logs for that error, but i guess it should be easily reproducible... should i update to hudson 1.341 in order for plugin to work?

          Yes, the Ivy Plugin 0.6 requires Hudson 1.341 or newer. That inner class you're referring to was only added to Hudson in 1.341

          Timothy Bingaman added a comment - Yes, the Ivy Plugin 0.6 requires Hudson 1.341 or newer. That inner class you're referring to was only added to Hudson in 1.341

          eguess74 added a comment -

          Yes the problem is still there. I'm running ivy plugin v 0.6 on hudson 1.341. One project has been misconfigured due to the bug in ivy plugin v0.3 which i submitted. The startup log took ~23Mb where the 99.5% of the file is filled up with repetitive error stack trace

          eguess74 added a comment - Yes the problem is still there. I'm running ivy plugin v 0.6 on hudson 1.341. One project has been misconfigured due to the bug in ivy plugin v0.3 which i submitted. The startup log took ~23Mb where the 99.5% of the file is filled up with repetitive error stack trace

          Ok, thanks for checking that, I'll have a look at it and see what I can do.

          Timothy Bingaman added a comment - Ok, thanks for checking that, I'll have a look at it and see what I can do.

          burghduffkc added a comment -

          In hudson version 1.386 I am seeing the same issue. In addition to the large log files, I am having ivy.xml files created that are zero bytes in size. I think this is happening because ivy/hudson is trying to resolve workspace files before the slaves are online. This happens with the ivy plugin versions 1.6, 1.7, 1.8, 1.13 and 1.14 ( These are the versions I tried )

          Log info

          java.io.FileNotFoundException: Can't stat file .....
          at hudson.ivy.IvyBuildTrigger.copyIvyFileFromWorkspaceIfNecessary(IvyBuildTrigger.java:262)
          at hudson.ivy.IvyBuildTrigger.recomputeModuleDescriptor(IvyBuildTrigger.java:293)
          at hudson.ivy.IvyBuildTrigger.getModuleDescriptor(IvyBuildTrigger.java:237)
          at hudson.ivy.IvyBuildTrigger.buildDependencyGraph(IvyBuildTrigger.java:385)
          at hudson.util.DescribableList.buildDependencyGraph(DescribableList.java:181)
          at hudson.model.Project.buildDependencyGraph(Project.java:168)
          at hudson.model.DependencyGraph.<init>(DependencyGraph.java:104)
          at hudson.model.Hudson.rebuildDependencyGraph(Hudson.java:3384)
          at hudson.model.Hudson$13.run(Hudson.java:2199)
          at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
          at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
          at hudson.model.Hudson$3.runTask(Hudson.java:691)
          at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
          at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
          at java.lang.Thread.run(Thread.java:619)

          .......

          INFO: Completed initialization
          Dec 7, 2010 1:20:23 PM hudson.TcpSlaveAgentListener <init>
          INFO: JNLP slave agent listener started on TCP port 12328

          burghduffkc added a comment - In hudson version 1.386 I am seeing the same issue. In addition to the large log files, I am having ivy.xml files created that are zero bytes in size. I think this is happening because ivy/hudson is trying to resolve workspace files before the slaves are online. This happens with the ivy plugin versions 1.6, 1.7, 1.8, 1.13 and 1.14 ( These are the versions I tried ) Log info java.io.FileNotFoundException: Can't stat file ..... at hudson.ivy.IvyBuildTrigger.copyIvyFileFromWorkspaceIfNecessary(IvyBuildTrigger.java:262) at hudson.ivy.IvyBuildTrigger.recomputeModuleDescriptor(IvyBuildTrigger.java:293) at hudson.ivy.IvyBuildTrigger.getModuleDescriptor(IvyBuildTrigger.java:237) at hudson.ivy.IvyBuildTrigger.buildDependencyGraph(IvyBuildTrigger.java:385) at hudson.util.DescribableList.buildDependencyGraph(DescribableList.java:181) at hudson.model.Project.buildDependencyGraph(Project.java:168) at hudson.model.DependencyGraph.<init>(DependencyGraph.java:104) at hudson.model.Hudson.rebuildDependencyGraph(Hudson.java:3384) at hudson.model.Hudson$13.run(Hudson.java:2199) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at hudson.model.Hudson$3.runTask(Hudson.java:691) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) ....... INFO: Completed initialization Dec 7, 2010 1:20:23 PM hudson.TcpSlaveAgentListener <init> INFO: JNLP slave agent listener started on TCP port 12328

            tbingaman Timothy Bingaman
            eguess74 eguess74
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: