[Pharo-project] multiple pharo images
How about Jenkins putting a build suffix to the images? -- something like * Pharo-2.0.build-20040.image* At the moment, all the build generate files with the same name. https://ci.lille.inria.fr/pharo/job/Pharo-2.0/41/ 2.0 #20040 Pharo-2.0.changes<https://ci.lille.inria.fr/pharo/job/Pharo-2.0/41/artifact/Pharo-2.0/Pharo-2....> 13069724[image: [fingerprint]]<https://ci.lille.inria.fr/pharo/job/Pharo-2.0/41/artifact/Pharo-2.0/Pharo-2....> Pharo-2.0.image<https://ci.lille.inria.fr/pharo/job/Pharo-2.0/41/artifact/Pharo-2.0/Pharo-2....> 18732936[image: [fingerprint]]<https://ci.lille.inria.fr/pharo/job/Pharo-2.0/41/artifact/Pharo-2.0/Pharo-2....> Pharo-2.0-one-click.zip<https://ci.lille.inria.fr/pharo/job/Pharo-2.0/41/artifact/Pharo-2.0-one-clic...> 19242637[image: [fingerprint]]<https://ci.lille.inria.fr/pharo/job/Pharo-2.0/41/artifact/Pharo-2.0-one-clic...> Pharo-2.0.zip<https://ci.lille.inria.fr/pharo/job/Pharo-2.0/41/artifact/Pharo-2.0.zip> 14962904[image: [fingerprint]]<https://ci.lille.inria.fr/pharo/job/Pharo-2.0/41/artifact/Pharo-2.0.zip/*fin...>
On 02/05/12 5:20 PM, Francisco Garau wrote:
How about Jenkins putting a build suffix to the images? -- something like *Pharo-2.0.build-20040.image*
At the moment, all the build generate files with the same name.
I prefer to have the same name, otherwise I have to do one of two things: (1) edit the build script of dependent jobs to have the new name, or (2) re-name the image and changes file to match the build script. I suspect that follow on build jobs is the reason for the current naming convention.
we envision an archiving facility with nicely named zips. but the artifacts in there will be the same name => otherwise scripting builds gets too annoying On 2012-05-02, at 23:29, Yanni Chiu wrote:
On 02/05/12 5:20 PM, Francisco Garau wrote:
How about Jenkins putting a build suffix to the images? -- something like *Pharo-2.0.build-20040.image*
At the moment, all the build generate files with the same name.
I prefer to have the same name, otherwise I have to do one of two things: (1) edit the build script of dependent jobs to have the new name, or (2) re-name the image and changes file to match the build script. I suspect that follow on build jobs is the reason for the current naming convention.
When you download a lot of images every week, this is nice to have a build number in order to recognize them. Regards, On Thu, May 3, 2012 at 4:20 AM, Francisco Garau <francisco.garau@gmail.com> wrote:
How about Jenkins putting a build suffix to the images? -- something like Pharo-2.0.build-20040.image
At the moment, all the build generate files with the same name.
https://ci.lille.inria.fr/pharo/job/Pharo-2.0/41/
2.0 #20040
Pharo-2.0.changes 13069724 Pharo-2.0.image 18732936 Pharo-2.0-one-click.zip 19242637 Pharo-2.0.zip 14962904
-- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/
Why not to have both :-) -- Pavel 3.5.2012 v 5:05, Serge Stinckwich <serge.stinckwich@gmail.com>:
When you download a lot of images every week, this is nice to have a build number in order to recognize them. Regards,
On Thu, May 3, 2012 at 4:20 AM, Francisco Garau <francisco.garau@gmail.com> wrote:
How about Jenkins putting a build suffix to the images? -- something like Pharo-2.0.build-20040.image
At the moment, all the build generate files with the same name.
https://ci.lille.inria.fr/pharo/job/Pharo-2.0/41/
2.0 #20040
Pharo-2.0.changes 13069724 Pharo-2.0.image 18732936 Pharo-2.0-one-click.zip 19242637 Pharo-2.0.zip 14962904
-- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/
On May 2, 2012, at 11:20 PM, Francisco Garau wrote:
How about Jenkins putting a build suffix to the images? -- something like Pharo-2.0.build-20040.image
+ 1 :)
At the moment, all the build generate files with the same name.
https://ci.lille.inria.fr/pharo/job/Pharo-2.0/41/
2.0 #20040
Pharo-2.0.changes 13069724 Pharo-2.0.image 18732936 Pharo-2.0-one-click.zip 19242637 Pharo-2.0.zip 14962904
participants (6)
-
Camillo Bruni -
Francisco Garau -
Pavel Krivanek -
Serge Stinckwich -
Stéphane Ducasse -
Yanni Chiu