|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
|
|
Getting exception when triggering downstream job.Hudson: 1.231
OS: Centos Standard build type The upstream build is setting its status to "success", however the downstream is not triggered. I've tried this with "Trigger even if the build is unstable" both checked and unchecked. No dice. The following stack is the last items of the upstream console. FATAL: Index: 0, Size: 0 java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.RangeCheck(ArrayList.java:546) at java.util.ArrayList.get(ArrayList.java:321) at hudson.model.DependencyGraph.sort(DependencyGraph.java:364) at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:132) at hudson.model.Build$RunnerImpl.cleanUp(Build.java:125) at hudson.model.Run.run(Run.java:815) at hudson.model.Build.run(Build.java:85) at hudson.model.ResourceController.execute(ResourceController.java:70) at hudson.model.Executor.run(Executor.java:85) |
|
|
Re: Getting exception when triggering downstream job.Thanks for the problem report. Fixed in 1.232. Ned Collyer wrote: > Hudson: 1.231 > OS: Centos > Standard build type > > The upstream build is setting its status to "success", however the > downstream is not triggered. > > I've tried this with "Trigger even if the build is unstable" both checked > and unchecked. No dice. > > The following stack is the last items of the upstream console. > > FATAL: Index: 0, Size: 0 > java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 > at java.util.ArrayList.RangeCheck(ArrayList.java:546) > at java.util.ArrayList.get(ArrayList.java:321) > at hudson.model.DependencyGraph.sort(DependencyGraph.java:364) > at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:132) > at hudson.model.Build$RunnerImpl.cleanUp(Build.java:125) > at hudson.model.Run.run(Run.java:815) > at hudson.model.Build.run(Build.java:85) > at hudson.model.ResourceController.execute(ResourceController.java:70) > at hudson.model.Executor.run(Executor.java:85) > -- Kohsuke Kawaguchi Sun Microsystems kohsuke.kawaguchi@... |
|
|
Re: Getting exception when triggering downstream job.Hmm, still happens in 1.232. Same exact stack trace as the one below.
Thanks, Jonathan Kelly
|
|
|
Re: Getting exception when triggering downstream job.D'oh! Sorry about that. Apparently I'm an idiot. When I noticed that it didn't automatically kick off a build for my downstream project, I went immediately to the "last succeeded build" (assuming that it had in fact succeeded) and noted the same stacktrace as I had seen before and thought that the bug was still there. Little did I know that I had just broken the build, so I wasn't actually viewing the most recent build...
Once again, sorry, Jonathan
|
| Free Forum Powered by Nabble | Forum Help |