Skip to main content



      Home
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 UserFriend
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:
  


Current Time: Tue Jul 08 17:59:33 EDT 2025

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

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

Back to the top