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. > >
