Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 381084

Summary:	Continuous Rebuilds with "Last build was not on tied node, forcing rebuild." message
Product:	Community	Reporter:	Marcel Bruch <marcel.bruch>
Component:	CI-Jenkins	Assignee:	Eclipse Webmaster <webmaster>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Marcel Bruch

2012-05-30 13:57:56 EDT

Hudson currently triggers our release build job automatically w/o any change in version control system.

The log says: "Last build was not on tied node, forcing rebuild." But as it is repeating the build since an hour or so, I think this should be investigated. Manually canceling doesn't work.



Build job: recommenders.release-e37




Started on May 30, 2012 1:53:01 PM
Using strategy: Default
[poll] Last Build : #109
[poll] Last Built Revision: Revision 22d51c9b0e9f34568fb3636743b1191a8f07aae1 (origin/dev/e37)
Last build was not on tied node, forcing rebuild.
Done. Took 0.88 sec
Changes found

Comment 1 Eclipse Webmaster

2012-05-31 10:02:26 EDT

I think this may have been caused by a 'reload configuration from disk' restart a couple of days ago.  I just restarted Hudson completely and the job queue seems pretty quiet.

-M.