On Friday, 1 April 2016 01:20:37 UTC+1, R Tyler Croy wrote:
>
> (replies inline)
>
> On Thu, 31 Mar 2016, Richard Bywater wrote:
>
> > It sounds to me like there's a good use-case for being able to skip the
> > setup wizard even in "prod" mode? Is the jenkins.install.runSetupWizard
> > ignored if development = false? If so would it make sense just to skip
> that
> > check?
>
>
> I agree, for stuff like puppet-jenkins the provisioning of the Jenkins
> master
> doesn't require the Getting Started wizard.
>
>
>
> If the system property that Baptiste referenced isn't fully turning the
> wizard
> off, then we need to fix that before RCs IMHO.
>
I'm currently testing this groovy script
/usr/share/jenkins/ref/init.groovy.d/set-install-state.groovy to hack
around this limitation:
```
import jenkins.model.*;
import hudson.util.*;
import jenkins.install.*;
j = Jenkins.getInstance()
uw = j.getInjector().getInstance(UpgradeWizard.class)
uw.setCurrentLevel(new VersionNumber("2.0"))
j.setInstallState(InstallState.INITIAL_SETUP_COMPLETED)
```
Today is the first time I've tried groovy though, so probably doing
something silly.
Are there any obvious improvements to the above?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/84b0aabd-8000-4381-88df-414f365230cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
