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.
There is no need to re-invent the wheel. The Athena Common Build
project is here to help, as it is the build solution we recommend to
our new projects. You can start here:
http://wiki.eclipse.org/Athena_Common_Build
There's also an IT Infra doc which may be helpful. Of course, since
there are many moving parts to Eclipse.org, it makes for a long doc.
http://wiki.eclipse.org/IT_Infrastructure_Doc
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.
Strangely, as someone who is skilled in *nix systems and php, but
not in Ant or Maven, my casual observation is that project teams
tend to reinvent the wheel when it comes to build. Some folks use
Athena, others, Ant, Maven, Tycho, Buckminster, PDE Build, b3, or
countless combinations of those technologies. Personally I find it
difficult to author a document when I don't know the starting point.
If I can help here in any way, please let me know. Investing this
time into improving Athena Common Build would be my preference.
Denis
|
