Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » 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 07:49
Kaz Nishimura is currently offline Kaz NishimuraFriend
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:
  


Current Time: Mon Aug 21 08:41:20 GMT 2017

Powered by FUDForum. Page generated in 0.02442 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software