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

Bug 345379

Summary: [releng] Move the RAP Build to the eclipse.org build infrastructure
Product: [RT] RAP Reporter: Holger Staudacher <holger.staudacher>
Component: RelengAssignee: Project Inbox <rap-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: P3    
Version: unspecified   
Target Milestone: 1.5 M1   
Hardware: All   
OS: All   
Whiteboard:
Bug Depends on: 345380, 345958, 345959    
Bug Blocks:    
Attachments:
Description Flags
Updated build scripts none

Description Holger Staudacher CLA 2011-05-11 04:50:48 EDT 
Currently we are building RAP at the EclipseSource Servers. To be more transparent we should move our build to the eclipse.org build infrastructure.

I think we should clone the build now and use it for productive use when the indigo release will be done.
Comment 1 Holger Staudacher CLA 2011-05-11 04:54:02 EDT 
I configured two hudson jobs which can be found here:
	https://hudson.eclipse.org/hudson/job/rap-tooling/
	https://hudson.eclipse.org/hudson/job/rap-runtime/

I will wright to the dev mailing list with further instructions. I think we should close this bug when we use these build productively.
Comment 2 Holger Staudacher CLA 2011-05-11 05:13:40 EDT 
Created attachment 195310 [details]
Updated build scripts

For this move I needed to update our build scripts. I only refactored the runtimeDir variable that it can be set by the Hudson.
Comment 3 Holger Staudacher CLA 2011-05-30 12:20:08 EDT 
Because we use CVS HEAD for 1.5 development I committed the attached scripts to CVS HEAD.
Comment 4 Rüdiger Herrmann CLA 2011-06-21 03:04:54 EDT 
The build is at eclipse.org and works. Can we close this bug?
Comment 5 Holger Staudacher CLA 2011-06-21 06:24:43 EDT 
As all indigo builds are done I think we can say that from now on the eclipse.org build is our primary build ;) I will close the bug.