Skip to content, Skip to search



1,666 bytes added, 09:56, 19 April 2016
no edit summary
#REDIRECT ImageJ has a [ Jenkins server]: a continuous integration system which automatically checks the code for build and test errors. Jenkins tests builds and performs [[releases]] for [[SciJava]] projects. It deploys <code>SNAPSHOT</code> builds to the [ ImageJ Maven repository] in response to pushes to each code repository's <code>master</code> branch. So any downstream projects depending on a version of <code>LATEST</code> for a given component will match the last successful Jenkins build—i.e., the latest code on <code>master</code>. Because every build also runs the associated [[wikipedia:Unit testing|unit tests]], Jenkins is instrumental in early detection of new bugs introduced to the codebase. You can access Jenkins's last successful build artifacts from the [[Downloads]] page. Jenkins also performs [[releases]], including [ automatically deploying ImageJ 1.x] and [ building installers for ImageJ 1.x]. Jenkins performs many other services too, such as keeping Git repository mirrors in sync, building javadocs and updating other web resources. == Travis CI == Developers of third party libraries and plugins can look at [[Travis]] for an open-source CI tool, with build configurations stored in the source repository itself. == Emotional Jenkins == Jenkins is ImageJ's robot butler! He does his job faithfully, and without rest. When things are going well, he is happy. But when code breaks, he can become sad, or even angry: [[Project management#Continuous_integrationFile:Emotional-jenkins.png]] Make sure you keep your code in shipshape if you want to avoid the butler's wrath!
Bureaucrat, emailconfirmed, incoming, administrator, uploaders