Found a solution for this issue. In previous releases, I had set this flag
via JENKINS_JAVA_OPTIONS in /etc/default/jenkins. If I move that same flag
from JENKINS_JAVA_OPTIONS to JAVA_ARGS in /etc/default/jenkins, it works as
expected.
On Wednesday, October 26, 2016 at 11:56:29 AM UTC-4,
Setting Djenkins.install.runSetupWizard=false doesn't seem to be working
correctly for me with more recent Jenkins releases. Setting that flag for
Jenkins 2.1 works fine, but that same flag doesn't work with the latest
release (2.27) or stable release (2.7.4). Is there a different flag that I
Adding a restart step to our Jenkins deployment script did the trick. The
java option to disable the setup wizard is working as well. Thanks!
On Monday, May 2, 2016 at 6:44:18 PM UTC-4, Daniel Beck wrote:
>
>
> > On 03.05.2016, at 00:15, Richard Bywater
> wrote:
> >
> >
> On 03.05.2016, at 00:15, Richard Bywater wrote:
>
> @Daniel - FYI I can't actually see a reply from you in this thread from April
> 21st. 6th April seems to be the last email from you in the thread.
I hate my email client :-(
Set the system property
Currently I'm creating 2 files:
/var/lib/jenkins/jenkins.install.UpgradeWizard.state
```
2.0
```
/var/lib/jenkins/init.groovy.d/basic-security.groovy
```
#!groovy
import jenkins.model.*
import hudson.security.*
def instance = Jenkins.getInstance()
println "--> creating local user 'admin'"
Any updates on this? I am also deploying Jenkins as part of a Vagrant
script that automatically downloads and deploys Jenkins to Tomcat, then
immediately begins running jobs via the CLI. When my vagrant script
downloaded the 2.0 release this morning, the new setup wizard essentially
blocked
On 05.04.2016, at 16:54, Stuart Warren wrote:
> Today is the first time I've tried groovy though, so probably doing something
> silly.
> Are there any obvious improvements to the above?
You could alternatively just go with patching the JENKINS_HOME so Jenkins
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
> >
(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?
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?
Richard.
On Fri, 1 Apr 2016 at 10:10 Baptiste Mathus
There's a sysprop for that, but normally only for development mode.
But, NOT FOR KIDS, you can confuse things by forcing it to dev mode.
Probably reasonable for continuously starting from scratch from the docker
container only, not for prod use obviously (beware that you may trigger
weird
Hello,
I am building a Docker container based on jenkinsci/jenkins:2.0-beta-1. I
am autofilling it in with jobs/pipelines but the annoying thing is that
every time I run the image I have to go through the setup wizard.
How do disable this wizard so that my container will just be up and
12 matches
Mail list logo