Re: Why have our Jenkins/Plugins *.hpi files changed to *.jpi files?

2016-11-09 Thread Stephen Connolly 
When you start up any Jenkins after something like 1.5xx then it will
automatically rename all .hpi files to .jpi

On 8 November 2016 at 16:55, Robert Kruck  wrote:

> 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  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.
>

-- 
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/CA%2BnPnMzvjchav54DGE6A8-kdEUeoZiaWc7JnNFdB%2BvFOyvvXYw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Why have our Jenkins/Plugins *.hpi files changed to *.jpi files?

2016-11-08 Thread Robert Kruck 
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  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.

Re: Why have our Jenkins/Plugins *.hpi files changed to *.jpi files?

2016-11-08 Thread Robert Kruck 
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 > 
> 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/bdef6722-8f31-45b3-87bd-72fa2f265ea9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Why have our Jenkins/Plugins *.hpi files changed to *.jpi files?

2016-11-08 Thread Daniel Beck 

> On 08.11.2016, at 15:59, Robert Kruck  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/628821B9-FDB8-4CDF-B069-08B647AA7301%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Why have our Jenkins/Plugins *.hpi files changed to *.jpi files?

2016-11-08 Thread Robert Kruck 
By timestamp I mean date plus time of day (hours, minutes, AM or PM)

For all of these renamed (from *.hpi to *.jpi), their "Date Modified" and 
"Date Created", without exception, are June 15, 2016 or earlier.

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.

Example, taken from Windows Explorer in the Jenkins/Plugin folder of one of 
our build machines (this file only last week was called versionnumber.hpi):

NameDate Modified   Date Created
versionnumber.jpi 6/15/2016 2:10 PM  9/16/2014  11:28 AM

+

On Tuesday, November 8, 2016 at 8:36:11 AM UTC-6, Daniel Beck wrote:

>
> > On 08.11.2016, at 15:29, Robert Kruck > 
> wrote: 
> > 
> > One would think a new filename would lead to a new timestamp for the 
> renamed file. 
>
> Not sure what you mean by 'timestamp'. mtime or ctime? Only the latter 
> changes on rename, and e.g. `ls -l` only shows the former. 
>
>

-- 
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/91c244ed-8604-47f2-9a70-689562638d1d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Why have our Jenkins/Plugins *.hpi files changed to *.jpi files?

2016-11-08 Thread Daniel Beck 

> On 08.11.2016, at 15:29, Robert Kruck  wrote:
> 
> One would think a new filename would lead to a new timestamp for the renamed 
> file.

Not sure what you mean by 'timestamp'. mtime or ctime? Only the latter changes 
on rename, and e.g. `ls -l` only shows the former.

-- 
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/12582D16-D013-4CA9-9496-855F45253E92%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Why have our Jenkins/Plugins *.hpi files changed to *.jpi files?

2016-11-08 Thread Robert Kruck 
ALL Jenkins plugins, in all three of our build servers which have Jenkins 
plugins, were in the past week renamed from *.hpi to *.jpi.

The timestamps of the renamed plugins are unchanged, the newest such 
timestamp is June 15, 2016.

I would expect that if some human intervention had occurred in the build 
machines - deliberately or by accident -  the timestamps of these Jenkins 
plugins, now ending in *.jpi, would now have November 2016 timestamps, but 
this is not the case, their timestamps remain June 15, 2016 or earlier, 
which is very confusing. One would think a new filename would lead to a new 
timestamp for the renamed file.

On Tuesday, November 8, 2016 at 8:12:37 AM UTC-6, Daniel Beck wrote:

> 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 > 
> 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-use...@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/36304936-fa5a-4158-bab9-53d23fe9d460%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Why have our Jenkins/Plugins *.hpi files changed to *.jpi files?

2016-11-08 Thread Daniel Beck 
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  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.