Preventing plugin setup wizard

[carlossg]

if I use

FROM jenkins:2.7.1
RUN echo 2.7.1 > /usr/share/jenkins/ref/jenkins.install.UpgradeWizard.state
RUN echo 2.7.1 > /usr/share/jenkins/ref/jenkins.install.InstallUtil.lastExecVersion

then I can avoid the wizard, but the admin password is not printed in the logs

Is there a way to just prevent the plugin setup?

[jglick]

Not sure. @kzantow do you know?

[kzantow]

If the initial admin user is actually created, it should print to the logs, see: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/install/SetupWizard.java#L91-L153

You may also want to pass -Djenkins.install.runSetupWizard=false to skip the initial setup altogether.

Optionally, you could cat $JENKINS_HOME/secrets/initialAdminPassword.

[kzantow]

If you actually just want to prevent the plugin setup, but you DO want the initial security setup, you can implement your own InstallStateFilter to alter the flow. You would need a plugin installed at boot time or to inject a class file into the war distribution, though. See: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/install/UpgradeWizard.java#L154 for a simple example.

[carlossg]

The problem with -Djenkins.install.runSetupWizard=false is that it is a runtime flag, not build time, vs. burning a file in the image
I'd say the typical flow is to build the image with some preconfigured plugins, then not ask for plugin setup at startup. Creating the admin user may be ok.

[kzantow]

Hm, is there any way to provide a properties file or set system properties at boot time? Maybe hook into this somehow? https://github.com/jenkinsci/extras-executable-war/blob/master/src/main/java/Main.java#L171

[carlossg]

at boot time yes, you can set JAVA_OPTS=-Djenkins.install.runSetupWizard=false
but I'm looking for something to do at build time, as it is then when the plugins are installed into the image

[kzantow]

I guess as things stand, either package it with a modification to the Main file I referenced to set the system property (or find a way to include a properties file in the distribution... or just add the command line flag to a run script if this is for a docker image). Or package a simple plugin that overrides the default behavior. It's trivial to do the latter, just involves actually making a plugin. I could send you an example, but it's basically the same as the UpgradeWizard I referenced: you just plug into the lifecycle, and set it to the RUNNING state, no matter what and It'll bypass the wizard (or wait until the security is configured and send it to the RUNNING state). There are a lot of solutions to this problem, let me know if I can help any other way.

[recena]

@carlossg Is there any update here?

[carlossg]

No updates. IIUC there is the option to skip the wizard but not a way to skip only plugin installation.

[kzantow]

@carlossg Again, a fairly trivial InstallStateFilter will do the trick, you just need to add a plugin with it before the app starts.

[carlossg]

@kzantow yes, I mean there is no way for someone extending the image to just do that easily with a file marker or something like that

[foxylion]

In our case we created a new Jenkins image which automatically installs some plugins and creates a admin user with a default password. So there is no Jenkins setup visible and after starting the container you can directly use Jenkins.
See here: https://github.com/foxylion/docker-jenkins

[carltonmason]

@foxylion I tried using the approach you described after looking at your Dockerfile but, I can't login to Jenkins. The Docker image built fine but when I try to login via the Jenkins web UI, I specify the default id and password that were also specified in the Dockefile and I get: Invalid login information. Please try again.

Never mind, I looked closer at your Dockerfile and figured it out....