Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-33568

Upgrading to 2.0 for an existing installation does not get the Getting Started dialogue

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • core
    • 2.0-alpha3

      People upgrading from 1.x installations that have $JENKINS_HOME/config.xml does not currently get the setup wizard dialog, which means they will not get any of the new functionalities that fresh installations is getting, most notably pipeline. This is unacceptable.

      Make sure upgrading users are steered into accepting the recommended set of plugins and enable security, while still providing an option to opt out of it for the few people who know what they are doing.

          [JENKINS-33568] Upgrading to 2.0 for an existing installation does not get the Getting Started dialogue

          Daniel Beck added a comment -

          Should probably accept either criterion for skipping the setup.

          Daniel Beck added a comment - Should probably accept either criterion for skipping the setup.

          I want to make sure upgrading users from 1.x do get the opportunity to install new set of plugins we are recommending.

          Kohsuke Kawaguchi added a comment - I want to make sure upgrading users from 1.x do get the opportunity to install new set of plugins we are recommending.

          R. Tyler Croy added a comment -

          kohsuke I strongly disagree with that kind of feature, it in effect breaks backwards compatibility as far as the user is concerned. If I upgrade to Jenkins 2.x and all of sudden nobody can access the web UI, that is a regression in functionality

          R. Tyler Croy added a comment - kohsuke I strongly disagree with that kind of feature, it in effect breaks backwards compatibility as far as the user is concerned. If I upgrade to Jenkins 2.x and all of sudden nobody can access the web UI, that is a regression in functionality

          I don't think we are saying different things Tyler. I'm just pointing out that if people upgrading from 1.x doesn't get to install new recommended set of plugins, what they see won't be that much different from 1.x, and that'd be a massive failure. You are saying when that happens, people shouldn't be locked out of web UI, which is also reasonable.

          What I think I was told was that for people upgrading, the getting started screen would only show up when people with admin rights come in. I also assumed, though perhaps incorrectly, that some portion will be skipped, such as the security dialog, if that is already configured.

          The comment from Daniel is getting me worried. I should take a look at this myself, too.

          Kohsuke Kawaguchi added a comment - I don't think we are saying different things Tyler. I'm just pointing out that if people upgrading from 1.x doesn't get to install new recommended set of plugins, what they see won't be that much different from 1.x, and that'd be a massive failure. You are saying when that happens, people shouldn't be locked out of web UI, which is also reasonable. What I think I was told was that for people upgrading, the getting started screen would only show up when people with admin rights come in. I also assumed, though perhaps incorrectly, that some portion will be skipped, such as the security dialog, if that is already configured. The comment from Daniel is getting me worried. I should take a look at this myself, too.

          It is critical that upgrading users get the same level of functionalities that those who are installing 2.0 fresh. But I hear what rtyler is saying.

          I wrote my proposal to wiki to address this.

          Kohsuke Kawaguchi added a comment - It is critical that upgrading users get the same level of functionalities that those who are installing 2.0 fresh. But I hear what rtyler is saying. I wrote my proposal to wiki to address this.

          Kohsuke Kawaguchi added a comment - - edited

          After further discussion, now the proposal is updated to tackle this in several stages. I'm going to file tickets to track those.

          Kohsuke Kawaguchi added a comment - - edited After further discussion, now the proposal is updated to tackle this in several stages. I'm going to file tickets to track those.

          step 0 & step 1 are in motion

          Kohsuke Kawaguchi added a comment - step 0 & step 1 are in motion

          Step 0 is done, the remaining work is post-beta/GA.

          Spike Washburn added a comment - Step 0 is done, the remaining work is post-beta/GA.

          Daniel Beck added a comment -

          Considering this resolved as the next step is tracked as JENKINS-33663

          Daniel Beck added a comment - Considering this resolved as the next step is tracked as JENKINS-33663

          Igor Tretyak added a comment -

          What is the URL of the upgrade wizard?
          I updated Jenkins, and then rebooted. After that, banner disappeared.

          Igor Tretyak added a comment - What is the URL of the upgrade wizard? I updated Jenkins, and then rebooted. After that, banner disappeared.

            Unassigned Unassigned
            rtyler R. Tyler Croy
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: