Community
Participate
Working Groups
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? :)
*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
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.
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
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.
