You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2020/09/25 02:19:00 UTC
[jira] [Commented] (BEAM-10903) beam_Release_NightlySnapshot -
failing to publish to apache.snapshot.https
[ https://issues.apache.org/jira/browse/BEAM-10903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17201851#comment-17201851 ]
Kenneth Knowles commented on BEAM-10903:
----------------------------------------
{{testPublicationLocal}} is publishing to a local directory. Full disk? We need the next level of root cause for sure.
> beam_Release_NightlySnapshot - failing to publish to apache.snapshot.https
> --------------------------------------------------------------------------
>
> Key: BEAM-10903
> URL: https://issues.apache.org/jira/browse/BEAM-10903
> Project: Beam
> Issue Type: Bug
> Components: test-failures
> Reporter: Daniel Oliveira
> Assignee: Tyson Hamilton
> Priority: P1
>
> CI: https://ci-beam.apache.org/job/beam_Release_NightlySnapshot/
> Example gradle scan: https://scans.gradle.com/s/u7djerswhtnfm
> Exceptions seem to have really long stack traces and varied error messages, so I don't want to copy-paste the whole thing, but this appears repeatedly:
> {noformat}
> Caused by: org.gradle.api.artifacts.PublishException: Failed to publish publication 'mavenJava' to repository 'apache.snapshots.https'
> {noformat}
> And the errors often boil down to failing to read some resource from repository.apache.org
> Actually, I spoke too soon. I found this line in some of the gradle scans too:
> {noformat}
> Caused by: org.gradle.api.artifacts.PublishException: Failed to publish publication 'mavenJava' to repository 'testPublicationLocal'
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)