[ 
https://issues.apache.org/jira/browse/CASSANDRA-18012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andres de la Peña updated CASSANDRA-18012:
------------------------------------------
          Fix Version/s: 3.0.29
                         3.11.15
                         4.0.9
                         4.1.1
                         5.0
    Source Control Link: 
https://github.com/apache/cassandra/commit/02048cffeae4267054541f96741b16b1d0d89a20
             Resolution: Fixed
                 Status: Resolved  (was: Ready to Commit)

> Remove -l / -m / -h designation and have two options: free or paid tier 
> circle config
> -------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-18012
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18012
>             Project: Cassandra
>          Issue Type: Task
>          Components: CI
>            Reporter: Josh McKenzie
>            Assignee: Andres de la Peña
>            Priority: Normal
>             Fix For: 3.0.29, 3.11.15, 4.0.9, 4.1.1, 5.0
>
>          Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> Currently the -h designation is wasteful and should not be used, and the -f 
> designation won't actually successfully run to completion.
> We should default to a "free tier" config (probably print a warning that it's 
> generating config w/subset of full tests that should not be used to validate 
> commits in big warning letters) that runs a subset of the test suites for 
> users working on patches to validate their work (unit test only? unit + 
> in-jvm dtest? TBD), and add a flag to generate a config using larger 
> containers + parallelization for the "paid" tier for folks w/paid circleci 
> accounts.,
> It looks like -p is available right now fwiw.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to