[
https://issues.apache.org/jira/browse/CASSANDRA-18618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738433#comment-17738433
]
Jacek Lewandowski edited comment on CASSANDRA-18618 at 6/29/23 8:34 AM:
------------------------------------------------------------------------
[https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/2528/]
[https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/760/workflows/e5a29baa-3ad2-49de-ad9d-a6e9de79cd70]
[https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/760/workflows/2a529c05-93ae-4120-a7fa-7575deb123a6]
was (Author: jlewandowski):
https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/2528/
> Update tasks configuration to run checks locally when requested
> ---------------------------------------------------------------
>
> Key: CASSANDRA-18618
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18618
> Project: Cassandra
> Issue Type: Task
> Components: Build
> Reporter: Jacek Lewandowski
> Assignee: Jacek Lewandowski
> Priority: Normal
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Currently CheckStyle and RAT are run with almost every single Ant target,
> which is annoying as when developing locally. The targets should be clear -
> "test" - runs the tests, "jar" - builds the project and creates jars, and
> then we should have a task "check" which runs all the static analysis, that
> is CheckStyle, RAT and Eclipse-Warnings (or whatever we decide to replace
> Eclipse-Warnings with).
> Such goal should be include in "artifacts" and we should run it instead of
> "eclipse-warnings" on CircleCI. This way building, static analysis and
> testings are clearly separated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
