ci-team / jimmy Goto Github PK

To avoid confusion with Jenkins plugins let's rename Jimmy plugins to modules

Let's have an initial version of automated release management.

Jimmy uses jenkins-cli to connect and configure Jenkins instance. We need a way to configure the SSH key used for the authentication

Jimmy needs to be a proper python package instead of a set of separate modules. This includes a repo restructure and setup.py fixes.

i.e. one should add

-Djenkins.install.runSetupWizard=false 

to JAVA_ARGS before the first start of jenkins service.

This will switch off the wizard and leave Jenkins instance unsecured, available for first setup by jimmy.

The other way is to create and configure cli_user manually before running the jimmy tool.

cli_user is used by jimmy for authentication in Jenkins Master instance.

We need to document it and configure it properly by default.

Probably setup autogenerated password?

Since our modules schemas are the main documentation source for the modules at the moment it'd be nice to have a user-friendly documentation pages generated from schema files.

These projects could be useful:

• https://github.com/lbovet/docson
• https://github.com/interagent/prmd

We need to have an ability to define custom scores for gerrit-trigger