Why work with the web interface of the Jenkins-CI or files.pharo.org
when you can easily download and manage the images you need/like 
directly from your Smalltalk tools:
 
Just try PharoLauncher:
 
http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher
 
Bye
T.
 
Gesendet: Freitag, 01. August 2014 um 18:23 Uhr
Von: "Eliot Miranda" <[email protected]>
An: "Pharo Development List" <[email protected]>
Betreff: Re: [Pharo-dev] where the...
 
 
On Thu, Jul 31, 2014 at 11:52 PM, Ben Coman <[email protected]> wrote:
Eliot Miranda wrote:
 
 
On Thu, Jul 31, 2014 at 9:48 PM, stepharo <[email protected]> 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.
 

cheers -ben
 
 
Stef

On 1/8/14 01:36, Eliot Miranda wrote:
*&^% do I find build artifacts for https://ci.inria.fr/pharo/job/Pharo-4.0/lastSuccessfulBuild/?  There's no pointer to an image/changes combo I can see.
--
Aloha,
Eliot
--
Aloha,
Eliot
--
Aloha,
Eliot

Reply via email to