Which plugins are affected by this? Jenkins normalized plugin names to jpi when extracting bundled plugins, when uploading through the UI, and when downloading from an update site. But rename of existing files doesn't happen AFAIK.
> On 08.11.2016, at 14:03, Robert Kruck <robertkru...@gmail.com> wrote: > > We have Jenkins plugins installed on three Jenkins Master build servers. > > Until very recently all Jenkins plugins files in the Jenkins/Plugins folders > of these three build servers had a filename ending in *.hpi. > > When I looked into these folders yesterday all the Jenkins plugins files now > have a filename ending in *.jpi. > > Timestamps of these *.jpi files are unchanged -- the newest timestamp is June > 15, 2016. > > There was no human intervention that could have caused this change in the > Jenkins plugins filenames from *.hpi to *.jpi. > > Has anyone else seen this? Does anyone know how this could have happened? How > can a Jenkins installation update its plugin filenames on its own, from *.hpi > to *.jpi, without human intervention? > > > -- > 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/d8febd04-6ce4-4506-8d88-324d88fd0f15%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- 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/70744B8C-47E0-4315-B07D-3A0D01D7908E%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
