[
https://issues.jenkins-ci.org/browse/JENKINS-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163524#comment-163524
]
Timothy Bingaman commented on JENKINS-10025:
--------------------------------------------
Hey guys,
apologies for not responding sooner. I'm afraid my time to work on this project
these days is pretty much nonexistent. Gregory Boissinot has taken over general
maintenance (gboissinot).
This particular issue is in the old Ivy trigger code as well, which is from
before I took over the project a number of years ago. All my effort was focused
on creating and maintaining the Ivy project type. I'm not sure how many people
are using the trigger vs the project type, but the trigger hasn't been actively
maintained for a fair while. That said, it may well be quite a simple fix to
resolve this issue, but I'm afraid I'm not going to have time to look into it.
-Timo
> Calling rebuildDependencyGraph() in cycle
> -----------------------------------------
>
> Key: JENKINS-10025
> URL: https://issues.jenkins-ci.org/browse/JENKINS-10025
> Project: Jenkins
> Issue Type: Bug
> Components: ivy
> Reporter: vjuranek
> Assignee: abayer
> Priority: Blocker
>
> There probably possible cycle call of rebuildDependencyGraph(),
> Ivy calls
> Hudson.getInstance().rebuildDependencyGraph();
> which starts following cycle:
> getModuleDescriptor() -> recomputeModuleDescriptor() -> setModuleDescriptor()
> -> hudson.model.Hudson.rebuildDependencyGraph()
> which results into StackOverflowError, for whole exception, see
> http://groups.google.com/group/jenkinsci-users/browse_thread/thread/3c6b67b448c98379#
--
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
