Eclipse Community Forums: Hudson » "Cascading job name set but the instance is not set." errors

Home » Archived » Hudson » "Cascading job name set but the instance is not set." errors

"Cascading job name set but the instance is not set." errors [message #1703272]

Thu, 30 July 2015 03:49

Eclipse User

I noticed the "Cascading job name set but the instance is not set." errors in the server log after upgrade to Hudson 3.3.0. I must reset the Cascading Job to fix the problems. Probably the job configurations were broken before the upgrade, but I am not sure why they have got broken.

[Updated on: Thu, 30 July 2015 03:53] by Moderator

Previous Topic:	Error installing using yum on CentOS
Next Topic:	Planning to rewrite a Mercurial plugin

Goto Forum:

-=] Back to Top [=-

Current Time: Tue Nov 04 01:29:27 EST 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter