[ImageJ-devel] [fiji-devel] Changes in ImgLib synchronization

[Curtis Rueden]

Hi Dscho,

> Should we set up a syncing job for ImageJ2?
>

> I just did that. I also added a tab "Synchronizers" to the Jenkins
> dashboard so you can easily have a look just at those jobs.
>

Rock on; it looks great.


> I also realized that our IJ1 synchronizer belongs into that group,
> although it is doubtful that the associated script is of any use to
> anybody except for us; IJ1 synchronization is just too specific to the
> layout of the IJ1 website.
>

Sure. But it is still useful for the community to be able to check the
status, and verify that the synchronization is working. And it serves as a
nice model for how one could do something similar to track other projects
that use tarballs instead of a public VCS.

Regards,
Curtis


On Wed, Feb 22, 2012 at 8:43 PM, Johannes Schindelin <
Johannes.Schindelin at gmx.de> wrote:

> Hi Curtis,
>
> On Wed, 22 Feb 2012, Curtis Rueden wrote:
>
> > > The IJ2 mirror is a Git-SVN mirror, so something slightly different.
> > > Also, I would like to keep the Jenkins job separate so that
> > > notifications about failures can be sent to different sets of email
> > > addresses.
> > >
> >
> > Good point. One thing we could do is clone the job every time we want to
> > keep a different repository in sync. That way there are separate
> > failures, separate emails, etc., as you point out.
> >
> > Should we set up a syncing job for ImageJ2 between
> > github.com/imagej/imagej.git and code.imagej.net:imagej.git and
> > fiji.sc/srv/git/imagej2/.git ?
>
> I just did that. I also added a tab "Synchronizers" to the Jenkins
> dashboard so you can easily have a look just at those jobs.
>
> I also realized that our IJ1 synchronizer belongs into that group,
> although it is doubtful that the associated script is of any use to
> anybody except for us; IJ1 synchronization is just too specific to the
> layout of the IJ1 website.
>
> Ciao,
> Dscho
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://imagej.net/pipermail/imagej-devel/attachments/20120223/7cb61f38/attachment.html>