, Mike Albert wrote:
>
> 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 r
lag that I
should be setting?
On Tuesday, May 3, 2016 at 11:44:13 AM UTC-4, Mike Albert wrote:
>
> 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
Did you ever find a solution for this? I'm trying to automate the JDK
installations for a new jenkins server.
Thanks.
On Friday, April 29, 2016 at 11:03:50 AM UTC-4, Stijn Diependaele wrote:
>
> Dear,
>
> I'm trying to write a groovy script which manages the JDK installs.
>
> The code below wo
For anyone else who stumbles upon this post via a Google Search, Karl found
a solution and it can be found in his repo below:
https://github.com/karlmdavis/ansible-jenkins2
Thanks Karl!
On Friday, April 8, 2016 at 5:41:29 PM UTC-4, Karl Davis wrote:
>
> Howdy all,
>
> As I mentioned in my last
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:
> >
> > @Daniel - FYI I can
Anybody else have a workaround for this? I tried adding
jenkins.install.UpgradeWizard.state and the groovy script to my install,
but I'm still being prompted to unlock jenkins after the install. Version
of my Jenkins install is below:
http://pkg.jenkins-ci.org/redhat/jenkins-2.1-1.1.noarch.rp
