Re: Generate SHA512 checksum
Sorry for not replying to this it got missed and then I went on holiday ;) On Fri, Mar 2, 2018 at 10:29 PM, Sathwik B P wrote: > Coming back the original problem, if other users are using gpg for signing > snapshots, due to the timestamping thing that came in 1.5.0, one would > experiece the same problem. That seems likely. I have not used the timestamping thing yet so yet to look into it. > Just for my understanding, can we hold the timestamp constant for the > lifetime of the build session using the same timestamp for all the > artifacts that gets uploaded during that session, this could probably solve > the above issue. No? yep. The way to do it would be to cache the timestamp the first time it is generated at and then return the cached value on future calls https://github.com/apache/buildr/blob/master/lib/buildr/packaging/artifact.rb#L84 On Fri, Mar 16, 2018 at 6:40 PM, Sathwik B P wrote: > FYI, releases to maven repo with higher SHA are not yet supported > [INFRA-16169]. > > We had to drop .sha512 for now and go with the default .md5,.sha1 checksums. Koolio. -- Cheers, Peter Donald
Re: Generate SHA512 checksum
Hi Peter,
FYI, releases to maven repo with higher SHA are not yet supported
[INFRA-16169].
We had to drop .sha512 for now and go with the default .md5,.sha1 checksums.
regards,
sathwik
On Fri, Mar 2, 2018 at 4:59 PM, Sathwik B P wrote:
> Peter,
>
> Thanks for the PR. Will have a build and let you know.
> I was wondering on the transport.rb upload but wasn't knowing how to pass
> the :digests with different values.
>digests = (options[:digests] || [:md5, :sha1, :sha512])
>
> Coming back the original problem, if other users are using gpg for signing
> snapshots, due to the timestamping thing that came in 1.5.0, one would
> experiece the same problem.
>
> Just for my understanding, can we hold the timestamp constant for the
> lifetime of the build session using the same timestamp for all the
> artifacts that gets uploaded during that session, this could probably solve
> the above issue. No?
> #{upload_name} comes up with a new timestamp everytime when the upload is
> called for each arfifact.
> https://github.com/apache/buildr/blob/master/lib/buildr/
> packaging/artifact.rb#L237
>
> regards,
> sathwik
>
> On Fri, Mar 2, 2018 at 4:20 PM, Peter Donald
> wrote:
>
>> Okay - had a chance to look at it. See what I did in
>> https://github.com/apache/ode/pull/5/files and hopefully that works
>> for you
>>
>> On Wed, Feb 28, 2018 at 6:11 PM, Sathwik B P
>> wrote:
>> > Hi Peter,
>> >
>> > We added it as rake file untill the buildr comes with an addon. I did
>> fix a
>> > couple of comilation issues.
>> > https://github.com/apache/ode/blob/ode-1.3.x/tasks/sha512.rake
>> >
>> > SHA512 digest is created for the artifacts but it's also creating
>> multiple
>> > copies of pom.xml for all sub modules.
>> > https://repository.apache.org/content/repositories/snapshots
>> /org/apache/ode/ode-axis2/1.3.8-SNAPSHOT/
>> >
>> > ode-axis2-1.3.8-20180228.064019-1.jar Wed Feb 28 06:40:22 UTC 2018
>> > 187851
>> > ode-axis2-1.3.8-20180228.064019-1.jar.md5 Wed Feb 28 06:40:23 UTC
>> 2018
>> > 32
>> > ode-axis2-1.3.8-20180228.064019-1.jar.sha1 Wed Feb 28 06:40:23 UTC
>> 2018
>> > 40
>> > ode-axis2-1.3.8-20180228.064019-1.pom Wed Feb 28 06:40:21 UTC 2018
>> > 22084
>> > ode-axis2-1.3.8-20180228.064019-1.pom.md5 Wed Feb 28 06:40:21 UTC
>> 2018
>> > 32
>> > ode-axis2-1.3.8-20180228.064019-1.pom.sha1 Wed Feb 28 06:40:22 UTC
>> 2018
>> > 40
>> > ode-axis2-1.3.8-20180228.064024-1.jar.sha512 Wed Feb 28 06:40:25
>> UTC
>> > 2018 128
>> > ode-axis2-1.3.8-20180228.064024-1.jar.sha512.md5 Wed Feb 28
>> 06:40:25
>> > UTC 2018 32
>> > ode-axis2-1.3.8-20180228.064024-1.jar.sha512.sha1 Wed Feb 28
>> 06:40:26
>> > UTC 2018 40
>> > ode-axis2-1.3.8-20180228.064024-1.pom Wed Feb 28 06:40:24 UTC 2018
>> > 22084
>> > ode-axis2-1.3.8-20180228.064024-1.pom.md5 Wed Feb 28 06:40:24 UTC
>> 2018
>> > 32
>> > ode-axis2-1.3.8-20180228.064024-1.pom.sha1 Wed Feb 28 06:40:25 UTC
>> 2018
>> > 40
>> > ode-axis2-1.3.8-20180228.064026-1.pom Wed Feb 28 06:40:26 UTC 2018
>> > 22084
>> > ode-axis2-1.3.8-20180228.064026-1.pom.md5 Wed Feb 28 06:40:27 UTC
>> 2018
>> > 32
>> > ode-axis2-1.3.8-20180228.064026-1.pom.sha1 Wed Feb 28 06:40:27 UTC
>> 2018
>> > 40
>> > ode-axis2-1.3.8-20180228.064026-1.pom.sha512 Wed Feb 28 06:40:28
>> UTC
>> > 2018 128
>> > ode-axis2-1.3.8-20180228.064026-1.pom.sha512.md5 Wed Feb 28
>> 06:40:28
>> > UTC 2018 32
>> > ode-axis2-1.3.8-20180228.064026-1.pom.sha512.sha1 Wed Feb 28
>> 06:40:28
>> > UTC 2018 40
>> >
>> > Any ideas?
>> >
>> > regards,
>> > sathwik
>> >
>> > On Thu, Feb 8, 2018 at 5:35 AM, Peter Donald
>> wrote:
>> >
>> >> Hi,
>> >>
>> >> I was going to see if I could whip up an addon but daddy duty calls so
>> >> all of I have got is the start of an addon at:
>> >>
>> >> https://gist.github.com/realityforge/51afcba9ae15458a6e027d881bb33d9c
>> >>
>> >> It was copied from the gpg addon and modified. It should be very close
>> >> to working if not complete but I have not even tried to run it.
>> >>
>> >> Hope that helps somewhat!
>> >>
>> >> On Wed, Feb 7, 2018 at 7:26 PM, Sathwik B P
>> wrote:
>> >> > Hi Guys,
>> >> >
>> >> > Is there a way we can generate SHA512 checksum for artifacts during
>> >> > upload/release task?
>> >> > [http://www.apache.org/dev/release-distribution#sigs-and-sums]
>> >> >
>> >> > We are on Buildr-1.5.3
>> >> >
>> >> > regards,
>> >> > sathwik
>> >>
>> >>
>> >>
>> >> --
>> >> Cheers,
>> >>
>> >> Peter Donald
>> >>
>>
>>
>>
>> --
>> Cheers,
>>
>> Peter Donald
>>
>
>
Re: Generate SHA512 checksum
Peter,
Thanks for the PR. Will have a build and let you know.
I was wondering on the transport.rb upload but wasn't knowing how to pass
the :digests with different values.
digests = (options[:digests] || [:md5, :sha1, :sha512])
Coming back the original problem, if other users are using gpg for signing
snapshots, due to the timestamping thing that came in 1.5.0, one would
experiece the same problem.
Just for my understanding, can we hold the timestamp constant for the
lifetime of the build session using the same timestamp for all the
artifacts that gets uploaded during that session, this could probably solve
the above issue. No?
#{upload_name} comes up with a new timestamp everytime when the upload is
called for each arfifact.
https://github.com/apache/buildr/blob/master/lib/buildr/packaging/artifact.rb#L237
regards,
sathwik
On Fri, Mar 2, 2018 at 4:20 PM, Peter Donald wrote:
> Okay - had a chance to look at it. See what I did in
> https://github.com/apache/ode/pull/5/files and hopefully that works
> for you
>
> On Wed, Feb 28, 2018 at 6:11 PM, Sathwik B P wrote:
> > Hi Peter,
> >
> > We added it as rake file untill the buildr comes with an addon. I did
> fix a
> > couple of comilation issues.
> > https://github.com/apache/ode/blob/ode-1.3.x/tasks/sha512.rake
> >
> > SHA512 digest is created for the artifacts but it's also creating
> multiple
> > copies of pom.xml for all sub modules.
> > https://repository.apache.org/content/repositories/
> snapshots/org/apache/ode/ode-axis2/1.3.8-SNAPSHOT/
> >
> > ode-axis2-1.3.8-20180228.064019-1.jar Wed Feb 28 06:40:22 UTC 2018
> > 187851
> > ode-axis2-1.3.8-20180228.064019-1.jar.md5 Wed Feb 28 06:40:23 UTC
> 2018
> > 32
> > ode-axis2-1.3.8-20180228.064019-1.jar.sha1 Wed Feb 28 06:40:23 UTC
> 2018
> > 40
> > ode-axis2-1.3.8-20180228.064019-1.pom Wed Feb 28 06:40:21 UTC 2018
> > 22084
> > ode-axis2-1.3.8-20180228.064019-1.pom.md5 Wed Feb 28 06:40:21 UTC
> 2018
> > 32
> > ode-axis2-1.3.8-20180228.064019-1.pom.sha1 Wed Feb 28 06:40:22 UTC
> 2018
> > 40
> > ode-axis2-1.3.8-20180228.064024-1.jar.sha512 Wed Feb 28 06:40:25 UTC
> > 2018 128
> > ode-axis2-1.3.8-20180228.064024-1.jar.sha512.md5 Wed Feb 28 06:40:25
> > UTC 2018 32
> > ode-axis2-1.3.8-20180228.064024-1.jar.sha512.sha1 Wed Feb 28
> 06:40:26
> > UTC 2018 40
> > ode-axis2-1.3.8-20180228.064024-1.pom Wed Feb 28 06:40:24 UTC 2018
> > 22084
> > ode-axis2-1.3.8-20180228.064024-1.pom.md5 Wed Feb 28 06:40:24 UTC
> 2018
> > 32
> > ode-axis2-1.3.8-20180228.064024-1.pom.sha1 Wed Feb 28 06:40:25 UTC
> 2018
> > 40
> > ode-axis2-1.3.8-20180228.064026-1.pom Wed Feb 28 06:40:26 UTC 2018
> > 22084
> > ode-axis2-1.3.8-20180228.064026-1.pom.md5 Wed Feb 28 06:40:27 UTC
> 2018
> > 32
> > ode-axis2-1.3.8-20180228.064026-1.pom.sha1 Wed Feb 28 06:40:27 UTC
> 2018
> > 40
> > ode-axis2-1.3.8-20180228.064026-1.pom.sha512 Wed Feb 28 06:40:28 UTC
> > 2018 128
> > ode-axis2-1.3.8-20180228.064026-1.pom.sha512.md5 Wed Feb 28 06:40:28
> > UTC 2018 32
> > ode-axis2-1.3.8-20180228.064026-1.pom.sha512.sha1 Wed Feb 28
> 06:40:28
> > UTC 2018 40
> >
> > Any ideas?
> >
> > regards,
> > sathwik
> >
> > On Thu, Feb 8, 2018 at 5:35 AM, Peter Donald
> wrote:
> >
> >> Hi,
> >>
> >> I was going to see if I could whip up an addon but daddy duty calls so
> >> all of I have got is the start of an addon at:
> >>
> >> https://gist.github.com/realityforge/51afcba9ae15458a6e027d881bb33d9c
> >>
> >> It was copied from the gpg addon and modified. It should be very close
> >> to working if not complete but I have not even tried to run it.
> >>
> >> Hope that helps somewhat!
> >>
> >> On Wed, Feb 7, 2018 at 7:26 PM, Sathwik B P wrote:
> >> > Hi Guys,
> >> >
> >> > Is there a way we can generate SHA512 checksum for artifacts during
> >> > upload/release task?
> >> > [http://www.apache.org/dev/release-distribution#sigs-and-sums]
> >> >
> >> > We are on Buildr-1.5.3
> >> >
> >> > regards,
> >> > sathwik
> >>
> >>
> >>
> >> --
> >> Cheers,
> >>
> >> Peter Donald
> >>
>
>
>
> --
> Cheers,
>
> Peter Donald
>
Re: Generate SHA512 checksum
Okay - had a chance to look at it. See what I did in https://github.com/apache/ode/pull/5/files and hopefully that works for you On Wed, Feb 28, 2018 at 6:11 PM, Sathwik B P wrote: > Hi Peter, > > We added it as rake file untill the buildr comes with an addon. I did fix a > couple of comilation issues. > https://github.com/apache/ode/blob/ode-1.3.x/tasks/sha512.rake > > SHA512 digest is created for the artifacts but it's also creating multiple > copies of pom.xml for all sub modules. > https://repository.apache.org/content/repositories/snapshots/org/apache/ode/ode-axis2/1.3.8-SNAPSHOT/ > > ode-axis2-1.3.8-20180228.064019-1.jar Wed Feb 28 06:40:22 UTC 2018 > 187851 > ode-axis2-1.3.8-20180228.064019-1.jar.md5 Wed Feb 28 06:40:23 UTC 2018 > 32 > ode-axis2-1.3.8-20180228.064019-1.jar.sha1 Wed Feb 28 06:40:23 UTC 2018 > 40 > ode-axis2-1.3.8-20180228.064019-1.pom Wed Feb 28 06:40:21 UTC 2018 > 22084 > ode-axis2-1.3.8-20180228.064019-1.pom.md5 Wed Feb 28 06:40:21 UTC 2018 > 32 > ode-axis2-1.3.8-20180228.064019-1.pom.sha1 Wed Feb 28 06:40:22 UTC 2018 > 40 > ode-axis2-1.3.8-20180228.064024-1.jar.sha512 Wed Feb 28 06:40:25 UTC > 2018 128 > ode-axis2-1.3.8-20180228.064024-1.jar.sha512.md5 Wed Feb 28 06:40:25 > UTC 2018 32 > ode-axis2-1.3.8-20180228.064024-1.jar.sha512.sha1 Wed Feb 28 06:40:26 > UTC 2018 40 > ode-axis2-1.3.8-20180228.064024-1.pom Wed Feb 28 06:40:24 UTC 2018 > 22084 > ode-axis2-1.3.8-20180228.064024-1.pom.md5 Wed Feb 28 06:40:24 UTC 2018 > 32 > ode-axis2-1.3.8-20180228.064024-1.pom.sha1 Wed Feb 28 06:40:25 UTC 2018 > 40 > ode-axis2-1.3.8-20180228.064026-1.pom Wed Feb 28 06:40:26 UTC 2018 > 22084 > ode-axis2-1.3.8-20180228.064026-1.pom.md5 Wed Feb 28 06:40:27 UTC 2018 > 32 > ode-axis2-1.3.8-20180228.064026-1.pom.sha1 Wed Feb 28 06:40:27 UTC 2018 > 40 > ode-axis2-1.3.8-20180228.064026-1.pom.sha512 Wed Feb 28 06:40:28 UTC > 2018 128 > ode-axis2-1.3.8-20180228.064026-1.pom.sha512.md5 Wed Feb 28 06:40:28 > UTC 2018 32 > ode-axis2-1.3.8-20180228.064026-1.pom.sha512.sha1 Wed Feb 28 06:40:28 > UTC 2018 40 > > Any ideas? > > regards, > sathwik > > On Thu, Feb 8, 2018 at 5:35 AM, Peter Donald wrote: > >> Hi, >> >> I was going to see if I could whip up an addon but daddy duty calls so >> all of I have got is the start of an addon at: >> >> https://gist.github.com/realityforge/51afcba9ae15458a6e027d881bb33d9c >> >> It was copied from the gpg addon and modified. It should be very close >> to working if not complete but I have not even tried to run it. >> >> Hope that helps somewhat! >> >> On Wed, Feb 7, 2018 at 7:26 PM, Sathwik B P wrote: >> > Hi Guys, >> > >> > Is there a way we can generate SHA512 checksum for artifacts during >> > upload/release task? >> > [http://www.apache.org/dev/release-distribution#sigs-and-sums] >> > >> > We are on Buildr-1.5.3 >> > >> > regards, >> > sathwik >> >> >> >> -- >> Cheers, >> >> Peter Donald >> -- Cheers, Peter Donald
Re: Generate SHA512 checksum
Hi Peter, We added it as rake file untill the buildr comes with an addon. I did fix a couple of comilation issues. https://github.com/apache/ode/blob/ode-1.3.x/tasks/sha512.rake SHA512 digest is created for the artifacts but it's also creating multiple copies of pom.xml for all sub modules. https://repository.apache.org/content/repositories/snapshots/org/apache/ode/ode-axis2/1.3.8-SNAPSHOT/ ode-axis2-1.3.8-20180228.064019-1.jar Wed Feb 28 06:40:22 UTC 2018 187851 ode-axis2-1.3.8-20180228.064019-1.jar.md5 Wed Feb 28 06:40:23 UTC 2018 32 ode-axis2-1.3.8-20180228.064019-1.jar.sha1 Wed Feb 28 06:40:23 UTC 2018 40 ode-axis2-1.3.8-20180228.064019-1.pom Wed Feb 28 06:40:21 UTC 2018 22084 ode-axis2-1.3.8-20180228.064019-1.pom.md5 Wed Feb 28 06:40:21 UTC 2018 32 ode-axis2-1.3.8-20180228.064019-1.pom.sha1 Wed Feb 28 06:40:22 UTC 2018 40 ode-axis2-1.3.8-20180228.064024-1.jar.sha512 Wed Feb 28 06:40:25 UTC 2018 128 ode-axis2-1.3.8-20180228.064024-1.jar.sha512.md5 Wed Feb 28 06:40:25 UTC 2018 32 ode-axis2-1.3.8-20180228.064024-1.jar.sha512.sha1 Wed Feb 28 06:40:26 UTC 2018 40 ode-axis2-1.3.8-20180228.064024-1.pom Wed Feb 28 06:40:24 UTC 2018 22084 ode-axis2-1.3.8-20180228.064024-1.pom.md5 Wed Feb 28 06:40:24 UTC 2018 32 ode-axis2-1.3.8-20180228.064024-1.pom.sha1 Wed Feb 28 06:40:25 UTC 2018 40 ode-axis2-1.3.8-20180228.064026-1.pom Wed Feb 28 06:40:26 UTC 2018 22084 ode-axis2-1.3.8-20180228.064026-1.pom.md5 Wed Feb 28 06:40:27 UTC 2018 32 ode-axis2-1.3.8-20180228.064026-1.pom.sha1 Wed Feb 28 06:40:27 UTC 2018 40 ode-axis2-1.3.8-20180228.064026-1.pom.sha512 Wed Feb 28 06:40:28 UTC 2018 128 ode-axis2-1.3.8-20180228.064026-1.pom.sha512.md5 Wed Feb 28 06:40:28 UTC 2018 32 ode-axis2-1.3.8-20180228.064026-1.pom.sha512.sha1 Wed Feb 28 06:40:28 UTC 2018 40 Any ideas? regards, sathwik On Thu, Feb 8, 2018 at 5:35 AM, Peter Donald wrote: > Hi, > > I was going to see if I could whip up an addon but daddy duty calls so > all of I have got is the start of an addon at: > > https://gist.github.com/realityforge/51afcba9ae15458a6e027d881bb33d9c > > It was copied from the gpg addon and modified. It should be very close > to working if not complete but I have not even tried to run it. > > Hope that helps somewhat! > > On Wed, Feb 7, 2018 at 7:26 PM, Sathwik B P wrote: > > Hi Guys, > > > > Is there a way we can generate SHA512 checksum for artifacts during > > upload/release task? > > [http://www.apache.org/dev/release-distribution#sigs-and-sums] > > > > We are on Buildr-1.5.3 > > > > regards, > > sathwik > > > > -- > Cheers, > > Peter Donald >
Re: Generate SHA512 checksum
Hi, I was going to see if I could whip up an addon but daddy duty calls so all of I have got is the start of an addon at: https://gist.github.com/realityforge/51afcba9ae15458a6e027d881bb33d9c It was copied from the gpg addon and modified. It should be very close to working if not complete but I have not even tried to run it. Hope that helps somewhat! On Wed, Feb 7, 2018 at 7:26 PM, Sathwik B P wrote: > Hi Guys, > > Is there a way we can generate SHA512 checksum for artifacts during > upload/release task? > [http://www.apache.org/dev/release-distribution#sigs-and-sums] > > We are on Buildr-1.5.3 > > regards, > sathwik -- Cheers, Peter Donald
