|RE: [cross-project-issues-dev] Need help publishing builds|
Quick summary of puzzle pieces:
http://wiki.eclipse.org/IT_Infrastructure_Doc - Basic info on working with the download server.
http://wiki.eclipse.org/Common_Build_Infrastructure/Publishing - Some overlap with above with discussion of using an ant-based promote.xml script that projects have to write and maintain.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=306854 - Request to create a push-button solution for getting builds from Hudson to the download server and cleaning up old builds. Good to see this discussed, but so far no visible progress and the bug is marked “helpwanted”. This seems to me a fundamental infrastructure piece and something that should be owned by the Foundation rather than left for the community.
So far, we are still missing the piece of creating the download page for the build and wiring that into the list of pages on the website. It looks like there are a 101 ways that projects have found to do this. Is there anything resembling best-practice? The approach used by the Modeling projects is the slickest that I’ve seen. Is that re-usable by others? Needless to say, this is something else that should be handled at the infrastructure level. Projects could publish a metadata file describing their artifacts and the pages could be synthesized by common infrastructure.
Note that I am not looking for a build system. There are many choices in this field and I already have a working build, including a Hudson job. Now I need the part that will publish the build once it is completed on Hudson. The next steps should not be dependent on the build system that was used to produce the zips.
I need to go from this:
To something like this:
On 08/10/2010 03:12 PM, Konstantin Komissarchik wrote:
Is there a document, wiki or anything similar that describes what must be done for a project to publish builds? Let’s assume that the project already has a build system and a Hudson job.
Has there been anything written that explains this stuff in detail? Let’s assume that the audience is Java developers with Ant or Maven experience, but not necessarily skilled in *nix systems or php. I’ve seen some references to “login to server x and setup a cron job”, which is frankly not very helpful for project teams without a dedicated releng person with admin background. Exact steps would be needed for everyone else.
This is a barrier that Eclipse Foundation should work on eliminating. There is no reason for every project to be doing this themselves and partially re-inventing the wheel in the process.
Back to the top