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

Bug 355779

Summary:	new jetty jobs
Product:	Community	Reporter:	Jesse McConnell <jesse.mcconnell>
Component:	CI-Jenkins	Assignee:	Eclipse Webmaster <webmaster>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	janet.campbell, mike.milinkovich, wayne.beaton
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Jesse McConnell

2011-08-24 20:47:06 EDT

I would like a new jetty job (2 actually) that would build a low traffic build based on a project not located at eclipse, its the other half (more like 1/6) of the project which is at the codehaus side.  We currently have it building over there on bamboo but it is problematic to have our project building in CI's in multiple locations, not to mention that bamboo is annoying.

jetty-7-codehaus
jetty-8-codehaus

This would build on commits over there which are pretty infrequent as the vast majority of the project is located at eclipse.

We would run on the linux machine and only ask that the dpkg and rpmutils deb's be installed that test our rpm and deb generation.

Would this be possible pretty please? :)

Comment 1 Jesse McConnell

2011-08-25 10:46:48 EDT

*cough* seeing the lawyer crew added and cc'd makes me want to be clearer that we will not _distribute_ the results of any of these builds directly, they would be purely a nice to have as we have been trying to integrate the community around jetty and avoid having the 'split brain' we have suffered with the project being spread over two locations.  Git has helped as we can now public and aggregate all our source checkins to one place

http://cia.vc/stats/project/jetty

what I am looking for is permission and the setup to build jetty7 and 8 codehaus bits in the same place as all the rest of our jetty7 and 8 work

Comment 2 Eclipse Webmaster

2011-08-25 10:58:16 EDT

Speaking only for Webmaster my concern here is that the Eclipse CI/build infra is only for Eclipse projects, and this sounds like 'I want to build a non-eclipse project here'.

-M.

Comment 3 Jesse McConnell

2011-08-25 11:10:37 EDT

well, that is exactly what I am looking for

this issue is filed under 'community' since this part of project is part of our jetty community and my hope is that we don't have to treat these two builds as complete outside entities, sure they are not eclipse projects per se but they are a part of the eclipse community in that they are a part of jetty :)

they would be low traffic low resource builds compared to the rest of jetty which is already building here

Comment 4 Wayne Beaton

2011-09-08 16:08:21 EDT

I understand that maintaining builds in different locations is painful. However, the answer has to be no. We cannot get into the business of using our already strained resources to build non-eclipse.org software. We can discuss if you'd like, but I'm marking this bug as WONTFIX.