TL;DR
Secure your jenkins
- ldap
- shell scripts output
- user/pwd
Manage diskspace requirement
- Install nagios checks for diskspace monitoring
- Install diskusage plugin
- Discard Old Builds
- Disable maven artefact archiving
Improve supportability
- maven -e option
- install job config history plugin
- use template project plugin
- groovy system scripts
TL
Secure your jenkins
configure jenkins to use your ldap or active directory. by default jenkins is really open… even “manage jenkins” is available to anonymous user.
you can disable logging of shell commands via
set +o interactive-comments set +o xtrace
there’s a plugin where you can centralize your user/password and that will mask them in the console logs
Manage diskspace requirement
Installl nagios checks for diskspace monitoring
Install diskusage plugin to gain visibility over the big consumer
Discard Old Buils
enable one of the 2 options :
Days to keep builds Max # of builds to keep
Disable maven artefact archiving
This option will tell jenkins to collect pom,jars,wars,ears as they are produced by maven. This is rarely usefull when you use an enterprise repository. This option is enabled by default… so you aren’t using it… disable it !
Build > Advanced > Disable automatic artifact archiving
Improve supportability
specify maven -e option
get detailed error from maven
install job config history plugin
knowing that something has changed in the project configuration is always good when something goes bad
use template project plugin
you can reuse builder, publisher from other projects.
get to know system groovy scripts. With a simple script you detect/fix the various highlighted issues in this post.
