Re: [cbi-dev] Publishing Build Artifacts

[Mikaël Barbero <mikael@xxxxxxxxxxx>]

Le 17 févr. 2016 à 14:30, erwindl0 <erwindl0@xxxxxxxxx> a écrit :

Thanks Mikael.

How does this relate to the ant step described by Ed Willink?

I don't know! I think Ed was talking about something specific to builds made with Buckminster.

regards

erwin

Op 17/02/2016 om 14:25 schreef Mikaël Barbero:

Hi Christoph,

Agreed that the documentation could be clearer. Please feel free to edit the wiki as you find things that are missing on it.

Your project ID is modeling.elk, so you have two spaces where you can put downloadable bits:

- /shared/modeling/elk, for temporary artifacts (snapshots, nightly, etc.). This folder is not backuped nor it is mirrored. The bits will be available at http://build.eclipse.org/modeling/elk
- /home/data/httpd/download.eclipse.org/modeling/elk for long term storage. This folder is backuped and mirrored. Note that symlinks are not supported to help mirrors work properly. The bits will be available at http://download.eclipse.org/modeling/elk

These folder are NFS mounted on every HIPP and on build.eclipse.org, so you can just copy your files over there as a post build step. You can also move them from /shared to /home/data/httpd/download.eclipse.org when you promote a build.

Feel free to fill bugs on Eclipse Foundation > Community > Servers if you have issues while accessing these folders.

Cheers,
Mikael

Note to Erwin: just replace modeling/elk by technology/triquetrum

Le 17 févr. 2016 à 13:39, Christoph Daniel Schulze <cds@xxxxxxxxxxxxxxxxxxxxxx> a écrit :

Hi everyone,

I'm having a bit of a hard time with our HIPP instance. Our automatic
builds are working beautifully, but I haven't seen many details in the
documentation on how to actually publish the artifacts to the downloads
area.

I tried looking at other Hudson configurations, but most are -- rightly
so -- not accessible to me, and the remaining ones I looked at are often
much more complex than what we currently require.

Here's what I've gathered so far:

- We should publish nightly builds to a descendant of /shared. Am I free
to choose the exact directory I put it in? As in, can I just copy our
artifacts to /shared/elk/nightly and link to
http://build.eclipse.org/elk/nightly or are there any other rules I'm
not aware of?

- Where is the long term storage mounted on our HIPP instance, and what
is the mapping to URLs we should link to?

It would be nice if the Hudson Wiki page could go into more detail on
these questions. :)

Cheers,
Christoph Daniel

_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev

_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev

_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail