Revision as of 08:41, 5 October 2017 (view source) Rueden (talk | contribs) (Slim down Jenkins section, explaining that we are transitioning to Travis and AppVeyor) ← Older edit		Revision as of 08:44, 5 October 2017 (view source) Rueden (talk | contribs) (Add Dev) Newer edit →
Line 9:		Line 9:
	For an up-to-date list, see the [https://jenkins.imagej.net/view/Active/ list of active Jenkins jobs].		For an up-to-date list, see the [https://jenkins.imagej.net/view/Active/ list of active Jenkins jobs].
		+
		+	[[Category:Development]]

---

Revision as of 08:44, 5 October 2017

Development
Topics Overview Philosophy Architecture Source code Project management Coding style Debugging
Tools GitHub Git Maven IDEs Travis AppVeyor Dotfiles
Guides Writing plugins ImageJ Ops Contributing to a plugin Distributing your plugins Development lifecycle Building a POM Developing with Eclipse Hands-on debugging Adding new ops Adding new formats Using native libraries Tips for developers Tips for C++ developers ImageJ 1.x plugins Versioning Logging Uber-JARs

ImageJ has a Jenkins server: a continuous integration system which automatically checks the code for build and test errors.

The ImageJ Jenkins currently performs a small number of key services:

• Automatic deployment of ImageJ 1.x and building of installers for ImageJ 1.x.
• Keeping Git repository mirrors in sync.

For an up-to-date list, see the list of active Jenkins jobs.