[
https://issues.apache.org/jira/browse/CASSANDRA-17712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17580460#comment-17580460
]
Stefan Miklosovic commented on CASSANDRA-17712:
-----------------------------------------------
Great idea, tired of hitting the same issue all over again, I do not know why
it is flaky. Sometimes it passes, sometimes it does not. "the right thing" is
to fix all Javadocs so they are nice and clean but that is gargantuan task at
this stage.
> Remove javadocs step from CI and release process
> ------------------------------------------------
>
> Key: CASSANDRA-17712
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17712
> Project: Cassandra
> Issue Type: Bug
> Components: CI
> Reporter: Berenguer Blasi
> Assignee: Brandon Williams
> Priority: Normal
>
> Currently the javadocs step is both:
> - Taking up jenkins cycles and generating a [large
> output|https://ci-cassandra.apache.org/job/Cassandra-trunk-artifacts/1313/jdk=jdk_1.8_latest,label=cassandra/consoleFull]
> in CI when building artifacts
> - Failing randomly on javadoc issues such as {{AlterTableStatement.java:135:
> error: text not allowed in element}}
> Apidocs are not being bundled, uploaded or used anywhere. Hence it would be
> best to remove javadocs generation on every CI. Mainly removing javadoc from
> artifacts and mvn-install.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
