This is the command I used: docker-compose run -v ~/.gnupg:/.gnupg dry-run
I'm running Docker 18.06.1-ce on Ubuntu 20.04.3 LTS. By the way, I was thinking of creating a "stage" branch in the Avatica git repo. We no longer use a branch per release (which is fine) but this means that the commit is not pushed to the git repo until after the vote passes. I propose to push the RC commit to the "stage" branch (and destructively force push if we need another RC) to give CI a chance to run on the RC. After the vote passes I will push a tag. Julian On Mon, Oct 4, 2021 at 10:48 AM Vladimir Sitnikov <[email protected]> wrote: > > I'm not sure which steps are you following, however, the same sequence > seems to work fine: > > Commands: > https://github.com/vlsi/vlsi-release-plugins/blob/83c85c5faa4c7cd1fe0173b75c1cba5e60c3f209/.github/workflows/release-test.yml#L33-L60 > Logs: > https://github.com/vlsi/vlsi-release-plugins/runs/3794304055?check_suite_focus=true > > Vladimir > > > пн, 4 окт. 2021 г. в 20:15, Julian Hyde <[email protected]>: > > > As release manager for the upcoming Avatica 1.19, I just tried to use > > the docker-based dry-run. I got the following failure: > > > > Build calcite-avatica FAILURE reason: > > Execution failed for task ':initializeNexusStagingRepository': > > java.io.UncheckedIOException: java.net.ConnectException: > > Failed to connect to /127.0.0.1:8080 > > at > > de.marcphilipp.gradle.nexus.internal.NexusClient.findStagingProfileId(NexusClient.kt:84) > > at > > de.marcphilipp.gradle.nexus.InitializeNexusStagingRepository.determineStagingProfileId(InitializeNexusStagingRepository.kt:113) > > at > > de.marcphilipp.gradle.nexus.InitializeNexusStagingRepository.access$determineStagingProfileId(InitializeNexusStagingRepository.kt:38) > > > > I don't want to spend a morning debugging Docker port-mappings so I'm > > moving on. > > > > Julian > >
