Hi Dscho,<br><br><blockquote style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">The IJ2 mirror is a Git-SVN mirror, so something slightly different. Also,<br>
I would like to keep the Jenkins job separate so that notifications about<br>
failures can be sent to different sets of email addresses.<br></blockquote>
<br>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.<br><br>Should we set up a syncing job for ImageJ2 between <a href="http://github.com/imagej/imagej.git">github.com/imagej/imagej.git</a> and code.imagej.net:imagej.git and <a href="http://fiji.sc/srv/git/imagej2/.git">fiji.sc/srv/git/imagej2/.git</a> ?<br>
<br>Regards,<br>Curtis<br><br><br><div class="gmail_quote">On Wed, Feb 22, 2012 at 10:39 AM, Johannes Schindelin <span dir="ltr"><<a href="mailto:Johannes.Schindelin@gmx.de">Johannes.Schindelin@gmx.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Curtis,<br>
<div class="im"><br>
On Wed, 22 Feb 2012, Curtis Rueden wrote:<br>
<br>
> > I worked pretty hard on the 2nd generation Git synchronizer which<br>
> > tries to keep our ImgLib repositories in sync (we now have already<br>
> > three public ImgLib repositories: one on <a href="http://fiji.sc" target="_blank">fiji.sc</a>, one on<br>
> > <a href="http://code.imagej.net" target="_blank">code.imagej.net</a> and one on GitHub).<br>
> ><br>
><br>
> Nice, thanks very much for this!<br>
><br>
> What do you think about combining the "Git-synchronizer" and<br>
> "Update-IJ2s-Git-Mirror" jobs into a single "Repository-synchronizer"<br>
> job? We can then add in additional repositories that require<br>
> synchronization in the future (there will be several more, including<br>
> imagej2).<br>
<br>
</div>The IJ2 mirror is a Git-SVN mirror, so something slightly different. Also,<br>
I would like to keep the Jenkins job separate so that notifications about<br>
failures can be sent to different sets of email addresses.<br>
<br>
Having said that, it probably makes sense to extract the git-svn mirroring<br>
into a script that could be used for other SVN mirroring jobs.<br>
<br>
Speaking of jobs, if we want to add tons of such jobs, we might need to<br>
make job groups in Jenkins like the NEST initiative has done...<br>
<div class="im"><br>
> > Relatedly, one thing I am planning to do is create a "scijava-base"<br>
> > project<br>
> of some kind in the <a href="http://github.com/scijava" target="_blank">github.com/scijava</a> space. Initially this would be<br>
> toplevel Maven POM containing common settings: use of Java 1.6, version<br>
> number constants to avoid version clashes between projects, a couple of<br>
> necessary hacks, etc. Currently, these settings are duplicated between<br>
> imagej2, imglib, imageja, scifio and loci-software project hierarchies.<br>
> It would be better for them all to inherit from scijava-base. While we<br>
> are at it, common scripts like the git-synchronizer could live there<br>
> too.<br>
<br>
</div>Makes sense!<br>
<br>
Ciao,<br>
Dscho<br>
</blockquote></div><br>