Intégration Continue

Ok, so here is a sketch of what we want, and how we can achieve it:

Goals:

• security enabled (most probably default to Jenkins’s own user database with Matrix-based security)
• a user account for the corresponding instance admin user
• a regular check that security is enabled
• a cimaster user with Administer rights (this is needed for administrative tasks such as safe-restart, and statistics)

We will use the config.xml, init.groovy script, and cron. At project creation:

• security is enabled in config.xml
• an init.groovy script is created which, on firstRun:
  • creates an admin user with an uuid-generated password (to be changed afterwards by the corresponding admin)
  • creates a cimaster user with a generic password, and the project's SSH key
• /etc/cron.d/jenkinsfarm is edited to add a line for periodically running a groovy script through the groovy jenkins-cli command. This script will check that the security is enabled.