Dear all,
I just changed the way our GitHub hook triggers Jenkins builds: I added a
custom hook that calls a PHP script:
https://github.com/imagej/github-email-hook
This script is highly configurable, and it only triggers the build when
the 'master' branch was updated. Furthermore, it actually triggers *two*
jobs: ImageJ-launcher and ImageJ (this is also something the default
GitHub hook cannot do).
Maybe I should also trigger the ImageJ-launcher-deploy? That way,
launchers for newly-tagged versions are always built and deployed first,
for use by ij-app's assembly...
The hook can be configured at http://code.imagej.net/github/hooks.php; you
will have to log in with your GitHub credentials.
Ciao,
Johannes
_______________________________________________
ImageJ-devel mailing list
[email protected]
http://imagej.net/mailman/listinfo/imagej-devel
