Hi Pavel, On Mon, Jul 9, 2012 at 1:32 PM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:

if you often download latest development Pharo versions from Jenkins, you may have a mess in the downloaded files because for all builds the archives and images have the same name. I created a Jenkins job that creates an archive named by the latest update number.

good idea. Wouldn't it be better to just change the name in the main job? -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

TX!!!! Indeed this was always a pain. On Jul 9, 2012, at 1:32 PM, Pavel Krivanek wrote:

Hi,

if you often download latest development Pharo versions from Jenkins, you may have a mess in the downloaded files because for all builds the archives and images have the same name. I created a Jenkins job that creates an archive named by the latest update number. So you will get something like this:

Pharo-2.0-20196.zip - Pharo-2.0-20196.image - Pharo-2.0-20196.changes - PharoV10.sources

link: https://ci.lille.inria.fr/pharo/view/Pharo%202.0/job/Pharo-2.0-Numbered/

-- Pavel