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

Rename update/install tracking files

XMLWordPrintable

      Right now, these two approaches are independent and partially redundant.

          [JENKINS-33805] Rename update/install tracking files

          Daniel Beck created issue -
          Daniel Beck made changes -
          Epic Link New: JENKINS-33810 [ 169285 ]

          Daniel Beck added a comment -

          kzantow Could you PTAL whether this can be handled towards 2.0 with reasonable effort? I suspect it might not.

          CC kohsuke

          Daniel Beck added a comment - kzantow Could you PTAL whether this can be handled towards 2.0 with reasonable effort? I suspect it might not. CC kohsuke
          Daniel Beck made changes -
          Assignee New: Keith Zantow [ kzantow ]
          Labels Original: 2.0 2.0-beta New: 2.0 2.0-beta 2.0-planned

          Kohsuke Kawaguchi added a comment -

          I left this comment in the original PR but I don't think this is achievable.

          What I think we should do instead is to rename the file that UpgradeWizard is using so that it is marked clearly as local to that one class, as opposed to try to be something more universally useful.

          Kohsuke Kawaguchi added a comment - I left this comment in the original PR but I don't think this is achievable. What I think we should do instead is to rename the file that UpgradeWizard is using so that it is marked clearly as local to that one class, as opposed to try to be something more universally useful.

          Keith Zantow added a comment -

          I think we should modify the InstallUtil version to be more of an update log. This could be in JSON format or something similar. We could use that to track all version upgrades, downgrades, and attach timestamps and metadata to each version, so things like this we could fairly easily track and display upgrade wizards at version 2.0, 2.1, etc.. Thoughts kohsuke tfennelly danielbeck?

          Keith Zantow added a comment - I think we should modify the InstallUtil version to be more of an update log. This could be in JSON format or something similar. We could use that to track all version upgrades, downgrades, and attach timestamps and metadata to each version, so things like this we could fairly easily track and display upgrade wizards at version 2.0, 2.1, etc.. Thoughts kohsuke tfennelly danielbeck ?

          Daniel Beck added a comment -

          kzantow Great idea, not towards 2.0 though. This issue is about investigating whether something can be done for that release to not introduce this redundant and possibly temporary system. If the answer is "no", that's a bit ugly but not the end of the world.

          Daniel Beck added a comment - kzantow Great idea, not towards 2.0 though. This issue is about investigating whether something can be done for that release to not introduce this redundant and possibly temporary system. If the answer is "no", that's a bit ugly but not the end of the world.
          Daniel Beck made changes -
          Epic Link Original: JENKINS-33810 [ 169285 ]
          Daniel Beck made changes -
          Labels Original: 2.0 2.0-beta 2.0-planned New: 2.0 2.0-beta

          Daniel Beck added a comment -

          Maybe just rename the files used by wizard step 0 so it's clear where they are from?

          Daniel Beck added a comment - Maybe just rename the files used by wizard step 0 so it's clear where they are from?
          Daniel Beck made changes -
          Labels Original: 2.0 2.0-beta New: 2.0 2.0-beta 2.0-planned

            kzantow Keith Zantow
            danielbeck Daniel Beck
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: