-
Bug
-
Resolution: Fixed
-
Blocker
According to danielbeck in this thread
You could alternatively just go with patching the JENKINS_HOME so Jenkins considers it not an update:
$ echo -n 2.0 > $JENKINS_HOME/upgraded
$ echo -n 2.0 > $JENKINS_HOME/.last_exec_versionThe files are being renamed in https://github.com/jenkinsci/jenkins/pull/2215, but for beta 2, the above appears to work.
But please note that this is considered internal storage so may not work this way forever. I think we'll pretty quickly introduce a supported alternative way though.
Based on comments by kzantow earlier in the 2.0 development cycle, I was under the impression that setting the system property jenkins.install.runSetupWizard=false would suffice.
Apparently this is not true.
For me, and my co-maintainer of the puppet-jenkins module jhoblitt, I believe the lack of a consistent and supported way to disable the "Getting Started" wizard is a blocker for 2.0. We cannot build reliable automation around provisioning Jenkins 2.0 (Puppet, Chef, etc) without it.
- links to
[JENKINS-34035] 2.0 needs a stable/supported way to disable the Getting Started wizard
| Assignee | New: Keith Zantow [ kzantow ] | |
| Labels | Original: 2.0 2.0-beta | New: 2.0 2.0-beta 2.0-planned |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Remote Link | New: This issue links to "PR 2223 (Web Link)" [ 14166 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
| Workflow | Original: JNJira [ 170054 ] | New: JNJira + In-Review [ 198775 ] |