Anyone is free to answer this question: Is there any scenario in which Jenkins plugins filenames, associated with Jenkins 2.5, might have had their plugin file extensions changed from *.hpi to *.jpi, in the absence of human intervention or human error?
++++++++++++++++++++++ On Tuesday, November 8, 2016 at 9:40:24 AM UTC-6, Robert Kruck wrote: > Based on your result, and based on the fact that no one in our group > touched Jenkins Plugins in any way (in our build servers), is it possible > that some sort of internal code in our Jenkins main installation (we are > using Jenkins 2.5, which was installed earlier this year) could have > changed on its own our Jenkins plugin file extensions from *.hpi to *.jpi? > > Or is this impossible and has this change occurred because of some human > error that occurred in the Jenkins\Plugins folders in our build machines? > > On Tuesday, November 8, 2016 at 9:19:26 AM UTC-6, Daniel Beck wrote: > >> >> > On 08.11.2016, at 15:59, Robert Kruck <robert...@gmail.com> wrote: >> > >> > I would expect all the renamed *.jpi Jenkins plugins to have "Date >> Modified" updated to November 2016, but the "Date Modified" for all the >> renamed *.jpi Jenkins plugins is June 15, 2016 or earlier. >> >> I just booted up a Windows 8.1 test VM and tried it: Renaming a file does >> not change the modification date on Windows. >> >> -- 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/5d4188a4-580c-4cf8-bbbd-3b1a1ebf72a4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
