On 01 Aug 2014, at 20:50, Cl��ment Bera <bera.clement@gmail.com> wrote:

2014-08-01 18:23 GMT+02:00 Eliot Miranda <eliot.miranda@gmail.com>:

On Thu, Jul 31, 2014 at 11:52 PM, Ben Coman <btc@openinworld.com> wrote:

Eliot Miranda wrote:

On Thu, Jul 31, 2014 at 9:48 PM, stepharo <stepharo@free.fr> wrote:

I can tell you that I do not like jenkins but we have it, it works and it is maintained. So I lobotomize myself when I use it and it looks ok :)

I like it very much. ��But there's a lot of freedom to design the server and make it easier to find results, etc. ��For example at Cadence Bob Westergaard has put a lot of effort into our Jenkins server with tabs grouping different build tasks by VM, Newspeak, Spur, etc. ��So I find it easier to navigate than the Pharo one. ��In particular it would be great if thee were pointers to the latest build artifacts on��https://ci.inria.fr/pharo/job/Pharo-4.0/. ��Is that possible?

I think the philosophy was to avoid the CI server also being a file sever - but perhaps the job result could provide a link to the associated uploaded http://files.pharo.org/image/40/xxxxx.zip

Ok, if one should go to files.pharo.org then there should be as many links to files.pharo.org in obvious places as possible. ��But if I, as an outside, think to myself "nbow where would I find the most recent build of Pharo 4?", I would go to the CI server.

For me, philosophically, a CI server /is/ a server, of build artifacts, test results and benchmarks.

��

I keep that link in my bookmarks to download the latest Pharo 4:

https://ci.inria.fr/pharo/job/Pharo-4.0-Update-Step-4-Publish/

However, to avoid the server to be overloaded (because there are many people downloading Pharo every day), it is better to use files.pharo.org .

We should add links to the CI server page. I put it on my TODO. (to be done *after* Holidays and ESUG).

Marcus