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

Bug 393617

Summary:	create puppet configuration for Hudson
Product:	z_Archived	Reporter:	Steffen Pingel <steffen.pingel>
Component:	Mylyn	Assignee:	Steffen Pingel <steffen.pingel>
Status:	CLOSED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	eclipse
Version:	unspecified
Target Milestone:	3.9
Hardware:	PC
OS:	Linux
Whiteboard:
Bug Depends on:
Bug Blocks:	386344

Description Steffen Pingel

2012-11-05 18:32:04 EST

Hudson and Jenkins servers should be managed through a puppet configuration.

Comment 1 Steffen Pingel

2012-11-10 10:27:09 EST

As Frank pointed out, Hudson 3.0 is not completely provisioned. The plug-in installation step is missing. I posted to the Hudson mailing list to clarify if a solution exists to automate that step: http://java.net/projects/hudson/lists/dev/archive/2012-11/message/7

Comment 2 Steffen Pingel

2012-11-12 16:59:24 EST

Response from Winston:

- When provisioning you could have a Hudson Home template that has these plugins in the plugins folder along with InitSetup.xml at the top level. In that case bootstrap screen does not appears. The content of InitSetup.xml is just one line

<string>Hudson 3.0 Initial Setup Done</string>

- Second option is, we are planning to release a bundle outside of Eclipse downloads (java.net), which has all these mandatory plugins bundled. You could use that.

Comment 3 Steffen Pingel

2012-11-12 16:59:38 EST

I think we'll wait for the java.net distribution before fully automating the setup and add a "human" step for now.

Comment 4 Steffen Pingel

2012-11-24 15:07:09 EST

The basics are in place. I have added a comment to bug 393141 about the Hudson 3.0 setup.