Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Need help publishing builds

its a royal pita for someone not indoctrinated to 'the eclipse way'

there are some ant scripts floating around that do all of the heavy
lifting, look for the athena common builder I think it was...I don't
have the link handy but those can get you going with the packing and
signing stuff (you'll need your account flagged as a signer so you
have access to the machine with the eclipse private key, webmaster can
help with that)

for jetty we use tycho and we wrote a maven plugin to manage the
process of packing, signing, repacking and updating checksums in
artifact.xml stuff.

so if your using maven Hugues and I can probably help you get going
with that, otherwise look for the athena goop.


jesse mcconnell

On Tue, Aug 10, 2010 at 14:12, Konstantin Komissarchik
<konstantin.komissarchik@xxxxxxxxxx> 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.
> I understand that something needs to move builds from Hudson to the
> downloads server. Then somehow these builds need to be listed on the project
> page. Then somehow these builds need to be managed/archived by the project
> team so that the download server doesn’t run out of space.
> 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. The current approach not only
> presents an unnecessary barrier for projects getting started at,
> but also leads to inconsistency between download pages of different
> projects. Frankly, other OSS hosts do much better in this area.
> In the meantime, if no consolidated wiki exists describing all of this
> information in detail, I will volunteer to put one together if someone will
> point me at all the pieces of this puzzle and help me figure out how it all
> fits together.
> - Konstantin
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx

Back to the top