[
https://issues.apache.org/jira/browse/CALCITE-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17431200#comment-17431200
]
Stamatis Zampetakis commented on CALCITE-4856:
----------------------------------------------
GitHub password authentications has been deprecated in many places so most
people will rely on tokens sooner or later. Note that if
\{{asfGitSourcePassword}} property is set to a GitHub token then the
\{{prepareVote}} task does not fail. Just leaving a comment here in case
somebody prefers to use GITHUB for pushing the release.
> Gradle prepareVote fails with 'not authorized'
> ----------------------------------------------
>
> Key: CALCITE-4856
> URL: https://issues.apache.org/jira/browse/CALCITE-4856
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Priority: Major
> Fix For: 1.29.0
>
>
> Gradle {{prepareVote}} fails with 'not authorized' error.
> {noformat}
> $ ./gradlew prepareVote -Prc=0 -Pasf
> > Configure project :
> Building Apache Calcite 1.28.0
> > Task :gitProps
> Execution optimizations have been disabled for task ':gitProps' to ensure
> correctness due to the following reasons:
> - Gradle detected a problem with the following location:
> '/home/jhyde/dev/release/calcite'. Reason: Task ':gitProps' uses this output
> of task ':babel:fmppMain' without declaring an explicit or implicit
> dependency. This can lead to incorrect results being produced, depending on
> what order the tasks are executed. Please refer to
> https://docs.gradle.org/7.2/userguide/validation_problems.html#implicit_dependency
> for more details about this problem.
> ...
> > Task :pushRcTag
> Pushing tag to Git remote release-origin:
> https://github.com/apache/calcite.git
> > Task :pushRcTag FAILED
> Build calcite FAILURE reason:
> Execution failed for task ':pushRcTag':
> Caused by: org.eclipse.jgit.api.errors.TransportException:
> https://github.com/apache/calcite.git: not authorized
> at org.eclipse.jgit.api.PushCommand.call(PushCommand.java:180)
> at
> com.github.vlsi.gradle.release.jgit.dsl.GitExtensionsKt.push(GitExtensions.kt:132)
> at
> com.github.vlsi.gradle.release.GitPushTask$pushTag$1.invoke(GitPushTask.kt:54)
> at
> com.github.vlsi.gradle.release.GitPushTask$pushTag$1.invoke(GitPushTask.kt:30)
> at
> com.github.vlsi.gradle.release.DefaultGitTask.jgit(DefaultGitTask.kt:45)
> at
> com.github.vlsi.gradle.release.GitPushTask.pushTag(GitPushTask.kt:50)
> at
> org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:104)
> at
> org.gradle.api.internal.project.taskfactory.StandardTaskAction.doExecute(StandardTaskAction.java:58)
> ...
> at
> org.eclipse.jgit.transport.Transport.push(Transport.java:1368)
> at org.eclipse.jgit.api.PushCommand.call(PushCommand.java:170)
> ... 89 more
> FAILURE: Build failed with an exception.
> * What went wrong:
> Execution failed for task ':pushRcTag'.
> > org.eclipse.jgit.api.errors.TransportException:
> > https://github.com/apache/calcite.git: not authorized
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output. Run with --scan to get full insights.
> * Get more help at https://help.gradle.org
> Deprecated Gradle features were used in this build, making it incompatible
> with Gradle 8.0.
> You can use '--warning-mode all' to show the individual deprecation warnings
> and determine if they come from your own scripts or plugins.
> See
> https://docs.gradle.org/7.2/userguide/command_line_interface.html#sec:command_line_warnings
> Execution optimizations have been disabled for 29 invalid unit(s) of work
> during this build to ensure correctness.
> Please consult deprecation warnings for more details.
> BUILD FAILED in 2m 32s
> 268 actionable tasks: 187 executed, 20 from cache, 61 up-to-date
> S3 cache 5s wasted (3s wasted on hits, 2s wasted on misses), reads: 43, hits:
> 20, elapsed: 5s, received: 8 KiB
> {noformat}
> I had tried previously without the {{-Pasf}} flag but that ran into other
> errors, sooner in the process, that seemed to be about my environment. I
> concluded that the dry-run was a waste of time.
> I'm not sure why the command is trying to push to github rather than gitbox.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
