CLI jar not updated with core

[jhoblitt]

The current logic for extracting jenkins-cli.jar from jenkins.war is not triggered when the core is updated.

[madAndroid]

We're experiencing this as well, and bit us today cc @AnneThor

…

On 14 Jul 2017 9:04 pm, "Joshua Hoblitt" ***@***.***> wrote: The current logic for extracting jenkins-cli.jar from jenkins.war is not triggered when the core is updated. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#782>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABQp3bQmXqzSV33ENA87M56ESURmPzZ4ks5sN7ungaJpZM4OYnwC> .

[jhoblitt]

I'm not sure what the best way to handle this is. A "big hammer" would be to extract the jar on every run. Another option would be to look at the filesize in the war and compare that to what is on disk. Yet another option would be make it trigger on notification from package installation.

[madAndroid]

That last option seems to me to be the safest - a notify on the package would ensure it's updated each time

…

On 14 Jul 2017 9:25 pm, "Joshua Hoblitt" ***@***.***> wrote: I'm not sure what the best way to handle this is. A "big hammer" would be to extract the jar on every run. Another option would be to look at the filesize in the war and compare that to what is on disk. Yet another option would be make it trigger on notification from package installation. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#782 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABQp3bcHA3d6zrPzQ2EVf_Qb2kKxXP0Bks5sN8CzgaJpZM4OYnwC> .

[joe-riley]

We are getting hit by this after updating. slave.jar and jenkins-cli.jar are corrupt. Is there a work around?