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

Help

Home

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

Show: Today's Messages :: Show Polls :: Message Navigator

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

Thu, 30 July 2015 07:49

Kaz Nishimura

Messages: 89
Registered: December 2014

Member

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.

Kaz Nishimura

[Updated on: Thu, 30 July 2015 07:53]

Report message to a moderator

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

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Oct 03 20:58:15 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter