Jenkins is a CI (Continuous Integration) tool which is used to widely to manage builds and tests. In this blog, I'm listing some of the add on's which makes Jenkins richer and support it's use to manage builds using Jenkins instead of homegrown scripts. Most of these additional functionality comes through Jenkins plugin's.
1) Support to GIT source code management
Plugin: Jenkins GIT plugin
It checkout code from GIT repository (using http/ssh/local/git protocol), poll for changes and trigger build
2) Archive the build artifacts (Post build section)
Provides link for download to artifacts which are built. It acts a one stop dashboard where you build and distribute artifacts to consumers. These artifacts are preserved as long as logs are preserved.
Plugin: Comes with default Jenkins download
3) Publishing Junit test result on build dashboard (Post build section)
If your project running junit tests, provide link to xml reports. Jenkins publish the test results , compose historical trends, web UI for viewing/tracking test results.
Plugin: Comes with default Jenkins download
4) Publishing Javadocs on build dashboard (Post build section)
If your project generating javadocs (for ex: mvn javadoc:javadoc), provide link to xml reports. Jenkins will publish the latest Javadoc and it can also retain older javadocs if needed.
Plugin: Comes with default Jenkins download
5) Publishing code coverage metrics ( ex: cobertura )
If your project calculating code coverage metrics (for ex: mvn cobertura:cobertura), provide link to xml reports generated by your coverage tools like cobertura/clover/Emma. Jenkins will publish the coverage metrics on job dashboard.
Plugin: Jenkins cobertura plugin
Cobertura plugin lets you to fine-tune minimum acceptable levels of code coverage.
6) Build trends
Clicking "trend" for a project displays build time trend, timeline graph (scroll your mouse on graph to see the historical build timings).
1) Support to GIT source code management
Plugin: Jenkins GIT plugin
It checkout code from GIT repository (using http/ssh/local/git protocol), poll for changes and trigger build
2) Archive the build artifacts (Post build section)
Provides link for download to artifacts which are built. It acts a one stop dashboard where you build and distribute artifacts to consumers. These artifacts are preserved as long as logs are preserved.
Plugin: Comes with default Jenkins download
3) Publishing Junit test result on build dashboard (Post build section)
If your project running junit tests, provide link to xml reports. Jenkins publish the test results , compose historical trends, web UI for viewing/tracking test results.
Plugin: Comes with default Jenkins download
4) Publishing Javadocs on build dashboard (Post build section)
If your project generating javadocs (for ex: mvn javadoc:javadoc), provide link to xml reports. Jenkins will publish the latest Javadoc and it can also retain older javadocs if needed.
Plugin: Comes with default Jenkins download
5) Publishing code coverage metrics ( ex: cobertura )
If your project calculating code coverage metrics (for ex: mvn cobertura:cobertura), provide link to xml reports generated by your coverage tools like cobertura/clover/Emma. Jenkins will publish the coverage metrics on job dashboard.
Plugin: Jenkins cobertura plugin
Cobertura plugin lets you to fine-tune minimum acceptable levels of code coverage.
6) Build trends
Clicking "trend" for a project displays build time trend, timeline graph (scroll your mouse on graph to see the historical build timings).
0 comments:
Post a Comment