Hi Daniel. It obviously worked locally, but I think it has to do with the Java version or something else with how it's run in Jenkins.
However, I want to make that more robust anyway, so I think I'll cancel this. On Fri, 3 Apr 2020 at 20:22, Daniel Klco <[email protected]> wrote: > Andrei, > > I'm seeing a test error on the build of 2233: > > https://builds.apache.org/blue/organizations/jenkins/Sling%2Fsling-org-apache-sling-testing-clients/detail/master/88/pipeline/ > > On Fri, Apr 3, 2020 at 12:26 PM Andrei Dulvac <[email protected]> wrote: > > > Hi, > > > > We solved 2 issues in each release: > > > > https://issues.apache.org/jira/projects/SLING/versions/12347772 > > > > https://issues.apache.org/jira/projects/SLING/versions/12344767 > > > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachesling-2233 > > > > https://repository.apache.org/content/repositories/orgapachesling-2234 > > > > You can use this UNIX script to download the release and verify the > > signatures: > > > https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD > > > > Usage: > > sh check_staged_release.sh 2233 /tmp/sling-staging > > > > sh check_staged_release.sh 2234 /tmp/sling-staging > > > > > > > > Please vote to approve this release: > > > > [ ] +1 Approve the release > > [ ] 0 Don't care > > [ ] -1 Don't release, because ... > > > > This majority vote is open for at least 72 hours. > > >
