I thought that replacing one of the files tracked by the MSI package would confuse the MSI package management facilities so that future upgrades using the MSI installer won't be allowed because one of the binary files managed by the MSI installer has been changed.
If future upgrades are always done by replacing the war file, that may be OK, but I would expect confusion or problems if a newer MSI installer is run after the jenkins.war file had been upgraded without using the MSI installer to do the upgrade. On Sun, Jul 19, 2020 at 8:07 PM Slide <slide.o....@gmail.com> wrote: > The method should be ok, the data for the jobs and such are not stored in > the same location as the "executable." I would definitely recommend always > backing up your JENKINS_HOME before installing new versions. > > On Sun, Jul 19, 2020, 18:49 PersonFirst PersonLast < > personandfri...@gmail.com> wrote: > >> Hello, >> I would like to check if what I did for upgrading existing Jenkins >> installation was OK/acceptable. I realize though it is not the documented >> method of upgrading Jenkins per my research after I performed the upgrade. >> >> 1. I have previously installed Jenkins using MSI file at Windows server a >> while ago. So, Jenkins runs as a service there. I performed many changes >> (new jobs provisioned, customized settings, installed various plugins) at >> this Jenkins installation since then. >> 2. I recently downloaded latest available LTS release (for Windows) of >> Jenkins from https://www.jenkins.io/download/ and installed Jenkins to >> the same location where existing Jenkins installation exists (e.g., >> indicated same path: C:\Program Files (x86)\Jenkins\). >> >> I didn’t see any issues so far with the above method but wanted to check >> if this method could have caused data loss (overwriting previous Jenkins >> settings, etc.) or the above method works just fine. >> >> Please let me know know if anyone has any questions or need additional >> information. >> Thank you >> PF >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to jenkinsci-users+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/CAKnF1n_GzUXHw5FkvgQhs7jjAoDmxtYVV0aEZBU192C01-ESjQ%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-users/CAKnF1n_GzUXHw5FkvgQhs7jjAoDmxtYVV0aEZBU192C01-ESjQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVd9iD6OoD5voGxbe7qvsO5tXV%3D%2BPx01MiGYtZkvG0i4NA%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVd9iD6OoD5voGxbe7qvsO5tXV%3D%2BPx01MiGYtZkvG0i4NA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFJAWeoMoNQU7GJcUnNDa2y8oWYnB0OV87r2hma--zcYQ%40mail.gmail.com.
