Re: ImageJ release cycle

Posted by dscho on Jun 03, 2013; 2:17am
URL: http://imagej.273.s1.nabble.com/ImageJ-release-cycle-tp5003165p5003192.html

Dear Wayne,

On Sun, 2 Jun 2013, Johannes Schindelin wrote:

> On Sat, 1 Jun 2013, Rasband, Wayne (NIH/NIMH) [E] wrote:
>
> > On May 31, 2013, at 9:43 PM, Johannes Schindelin wrote:
> >
> > > On Fri, 31 May 2013, Rasband, Wayne (NIH/NIMH) [E] wrote:
> > >
> > >> On May 31, 2013, at 10:48 AM, Johannes Schindelin wrote:
> > >>
> > >>> Wayne, I would be very happy to contribute my experience and
> > >>> knowledge about the continuous release management to install a new
> > >>> job on our continuous integration server to create ImageJ packages
> > >>> for every new minor version and and for all "nightly builds"
> > >>> automatically.
> > >>
> > >> I am interested. Would the continuous integration server support
> > >> the Inno Setup installer used with the Windows packages? As far as
> > >> I know, it only runs on Windows.
> > >
> > > There are ways to get it to run on Linux, but our setup includes
> > > Windows nodes (e.g. for building the ImageJ launcher for Windows).
> > >
> > > I managed to extract .iss scripts from all three Windows installers,
> > > but of course it would be better if you would be willing to provide
> > > yours?
> >
> > Here is the .iss script I use to generate all three installers. With
> > the version bundled with 64-bit Java, I uncomment this line:
> >
> >     ;ArchitecturesInstallIn64BitMode=x64
>
> I got that far by inspecting the extracted .iss files. What I missed
> (which innounp is apparently not able to detect) is the 'users-modify'
> permission on the directory.
>
> So here is the result of my work so far:
>
> http://jenkins.imagej.net/job/ImageJ1-releases/label=Windows/
> and
> http://jenkins.imagej.net/job/ImageJ1-releases/label=master/
>
> Note: MacOSX needs work, I concentrated on Linux and Windows (which should
> be fine).
>
> The job is configured to take http://imagej.net/ij/ij.jar, extract its
> version, and make all of the installers/archives at 11pm CDT every night.

In the meantime, I also got MacOSX to work properly (generated in the
'master' configuration).

I also changed the configuration so that http://imagej.net/ij.jar is used,
and the job inspects every 15 minutes whether that URL's timestamp has
changed (and builds when it has).

Wayne, could you have a look whether everything works as you expect it? In
particular, I would suggest to verify that Jenkins schedules a build
within 15 minutes of you uploading a new ij.jar.

Ciao,
Johannes

P.S.: Of course the complete project to make these releases is maintained
in a repository with development history, too:
https://github.com/imagej/ij1-installer (I will add a README.md later, for
now I am done with working this weekend)

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html