Login  Register

Re: ImageJ release cycle

Posted by dscho on Jul 08, 2013; 4:54pm
URL: http://imagej.273.s1.nabble.com/ImageJ-release-cycle-tp5003165p5003823.html

Dear Wayne,

On Mon, 3 Jun 2013, Rasband, Wayne (NIH/NIMH) [E] wrote:

> Dear Johannes,
>
> On Jun 2, 2013, at 10:17 PM, Johannes Schindelin wrote:
>
> > 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).
>
> As I said yesterday, running the job only when there is a new letter
> release (e.g. 1.47s but not 1.47s1) would be fine.

I hope you do not mind the current solution, as excluding 1.47s1
explicitly would be a lot more work because I cannot skip a build when it
already started (and I would have to inspect the *contents* of ij.jar as
downloaded from the ImageJ 1.x website to find out what type of version it
represents as there is no other mechanism by which I could possibly tell).

Also: the description (which is now updated after every build) as well as
the color-coded badges contributed by Jerome should make it much easier to
navigate the page http://jenkins.imagej.net/job/ImageJ1-releases/

> It might be a good idea, however, to run the unit tests on each daily
> build.

Unfortunately, this is not as easy as you might think: the unit tests are
a full-fledged Maven project, expecting ImageJ 1.x in the same form (as
you know, ImageJA is now nothing more than a Mavenized project following
the minor versions as published by you on http://imagej.net/notes.html and
http://imagej.net/download/src/ (if those two disagree on the latest
version, the Jenkins job keeping ImageJA up-to-date refuses to update
anything).

So to support what you ask for, I would have to

- make a new Jenkins job
- let that job monitor the daily builds
- finagle the ij.jar into a pseudo-Maven repository
- let the unit-tests run on that faked Maven artifact

I will find those hours later this week to make that happen, but it will
be a different job from ImageJ1-unit-tests because those two jobs share
only the spirit, not the procedure.

Ciao,
Johannes

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