Disable setup wizard about configuration-as-code-plugin HOT 9 CLOSED

Could we add a validation of sorts that prevents disabling the wizard without defining authn + authz?

from configuration-as-code-plugin.

sounds reasonable.
A quick look at SetupWizard seems to demonstrate there's no simple way to disable it programmatically anyway :-\

from configuration-as-code-plugin.

The system property jenkins.install.runSetupWizard is used from InstallState, but there's no field you can set for this, true.

from configuration-as-code-plugin.

possible workaround:
introduce a servlet filter to force UpgradeWizard#SHOW_UPGRADE_WIZARD_FLAG session attribute

from configuration-as-code-plugin.

during post-FOSDEM hackathon it was decided we don't need to support case:

• without docker
• start from empty system
• launch Jenkins with jenkins.yaml

in case of docker or pre-existing Jenkins instance issue is not present

it is possible though to provide a set of scripts that will take care of skipping the wizard and pre-installing the plugin, but it won't be part of this project -> closing the ticket

from configuration-as-code-plugin.

@ewelinawilkosz AFAIK the setup wizard also needs to be circumvented when running Jenkins in Docker.
In its current state JCasC doesn't seem to actually support new Jenkins installations at all.

from configuration-as-code-plugin.

@deiga instead of poking around in old issues, I suggest you join the chat on gitter

Here is the solution you can use in docker.
Honestly, this is a docker issue, not a JCasC issue.

RUN echo $JENKINS_VERSION | tee \
    $jenkins_home/jenkins.install.UpgradeWizard.state \
    $jenkins_home/jenkins.install.InstallUtil.lastExecVersion

from configuration-as-code-plugin.

See also #393

from configuration-as-code-plugin.

Note that in the above you'll want JENKINS_HOME with the jenkins/jenkins Docker images, not jenkins_home.

from configuration-as-code-plugin.