Hey Julian,
I just tested everything in docker and it works if I do the following:
Terminal 1:
git clone https://github.com/vlsi/asflike-release-environment
cd asflike-release-environment
./recreate.sh calcite-avatica
... wait for the mock release environment to finish starting ...
Terminal 2:
git clone https://github.com/apache/calcite-avatica
cd calcite-avatica
docker-compose run -v ~/.gnupg:/.gnupg dry-run
This is the result:
--- snipped ---
> Task :createRcTag
Created tag avatica-1.19.0-rc0 ->
Ref[refs/tags/avatica-1.19.0-rc0=2df9697c97350c9e92f9336c2b8c1270076e45a9(-1)]
> Task :pushRcTag
Pushing tag to Git remote release-origin-test:
git://127.0.0.1/calcite-avatica.git
Message from release-origin-test:
refs/tags/avatica-1.19.0-rc0: OK,
2df9697c97350c9e92f9336c2b8c1270076e45a9 (fastForward)
> Task :generateVoteText
Listing SVN folders [] at
http://127.0.0.1/svn/dist/dev/calcite/apache-calcite-avatica-1.19.0-rc0
Fetching
http://127.0.0.1/svn/dist/dev/calcite/apache-calcite-avatica-1.19.0-rc0/apache-calcite-avatica-1.19.0-src.tar.gz.sha512@2
Please find draft vote text in /src/build/prepareVote/mail.txt
> Task :prepareVote
--- vote email snipped ---
Deprecated Gradle features were used in this build, making it
incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See
https://docs.gradle.org/6.8.3/userguide/command_line_interface.html#sec:command_line_warnings
BUILD SUCCESSFUL in 5m 8s
105 actionable tasks: 105 executed
Francis
On 5/10/2021 7:40 am, Stamatis Zampetakis wrote:
I haven't done an avatica release so I don't know if using docker is must
but maybe running directly the prepareVote task could work:
./gradlew prepareVote -Prc=0 -Pasf
It may complain about missing properties. I have the following on my
~/.gradle/gradle.properties file:
useGpgCmd=true
signing.gnupg.executable=gpg
signing.gnupg.useLegacyGpg=false
signing.gnupg.keyName=D77C3383F1927570
signing.gnupg.passphrase=XXXX
asfSvnUsername=zabetak
asfSvnPassword=YYY
asfGitSourceUsername=zabetak
asfGitSourcePassword=ZZZZ
asfNexusUsername=zabetak
asfNexusPassword=YYY
Best,
Stamatis
On Mon, Oct 4, 2021 at 10:03 PM Julian Hyde <[email protected]> wrote:
I'm still running into this 'Connection refused' error. It's a
show-stopper. I cannot make a release candidate unless this problem is
solved.
On Mon, Oct 4, 2021 at 10:58 AM Julian Hyde <[email protected]> wrote:
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
