I've now registered:
https://issues.jenkins-ci.org/browse/JENKINS-14616
kl. 12:54:02 UTC+2 fredag 27. juli 2012 skrev DarkRift følgende:
>
> Then a simple sha1 validation once the file has been completely downloaded
> would solve the issue...
>
> I'd look into it but I didn't receive my laptop y
Then a simple sha1 validation once the file has been completely downloaded
would solve the issue...
I'd look into it but I didn't receive my laptop yet from the repair center.
Should be easy enough to add anyhow if any one want to contribute a patch for
this improvment.
Richard
On 2012-07-27
Thank you for the quick responses. I've now forwarded the request to
https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-dev/ueaAOGrtVDI
kl. 12:45:09 UTC+2 fredag 27. juli 2012 skrev Stephen Connolly følgende:
> update center incudes the sha1 of the file
>
> On 27 July 2012 11:41, Richar
update center incudes the sha1 of the file
On 27 July 2012 11:41, Richard Lavoie wrote:
> This should be relatively easy with CRC or MD5 content check once
> downloaded but I don't know if the plugin repository gives that information
> to jenkins already.
>
> Richard
>
>
>
> On 2012-07-27, at 06
This should be relatively easy with CRC or MD5 content check once downloaded
but I don't know if the plugin repository gives that information to jenkins
already.
Richard
On 2012-07-27, at 06:31, Sami Tikka wrote:
> That's an excellent idea. I believe there already is some verification in th
That's an excellent idea. I believe there already is some verification in the
plugin loading process but maybe it happens too late.
jenkins-users list, however, is mostly visited by ... users of jenkins. If you
want someone to actually do something, you could find jenkins developers on the
jenk
