[ 
https://issues.apache.org/jira/browse/CASSANDRA-14806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16792901#comment-16792901
 ] 

Stefan Podkowinski commented on CASSANDRA-14806:
------------------------------------------------

Looks like your latest builds can be found at:

 * [2.2|https://circleci.com/workflow-run/6ac9d6c4-3968-4a6e-8cbe-cad8c7880961]
 * [3.0|https://circleci.com/workflow-run/50120c8c-8641-4761-aaa2-64214ed9290a]
 * [3.11|https://circleci.com/workflow-run/db5e3bb2-4b8a-456a-8d5b-6dc943fea0fe]
 * 
[trunk|https://circleci.com/workflow-run/e1eec049-70f1-4a07-b3e9-1c519cb26888]

There seems to be a significant number of 2.2 dtests (see also CASSANDRA-14866) 
and the upgrade tests failing, so I did some reference runs against the 
unmodified branches. Turns out we see the same kind of failures there as well, 
so it shouldn't be related to the patch at all.
 * [3.0 - upgrade 
tests|https://circleci.com/gh/spodkowinski/cassandra/675#tests/containers/11]
 * [3.11 - upgrade 
tests|https://circleci.com/gh/spodkowinski/cassandra/673#tests/containers/11]
 * [2.2 - 
dtests|https://circleci.com/workflow-run/0dae4fa9-7b00-4814-9726-87ad513bb110]

+1, I think we're ready to get this merged now. 

> CircleCI workflow improvements and Java 11 support
> --------------------------------------------------
>
>                 Key: CASSANDRA-14806
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14806
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Build, Legacy/Testing
>            Reporter: Stefan Podkowinski
>            Assignee: Stefan Podkowinski
>            Priority: Normal
>
> The current CircleCI config could use some cleanup and improvements. First of 
> all, the config has been made more modular by using the new CircleCI 2.1 
> executors and command elements. Based on CASSANDRA-14713, there's now also a 
> Java 11 executor that will allow running tests under Java 11. The {{build}} 
> step will be done using Java 11 in all cases, so we can catch any regressions 
> for that and also test the Java 11 multi-jar artifact during dtests, that 
> we'd also create during the release process.
> The job workflow has now also been changed to make use of the [manual job 
> approval|https://circleci.com/docs/2.0/workflows/#holding-a-workflow-for-a-manual-approval]
>  feature, which now allows running dtest jobs only on request and not 
> automatically with every commit. The Java8 unit tests still do, but that 
> could also be easily changed if needed. See [example 
> workflow|https://circleci.com/workflow-run/be25579d-3cbb-4258-9e19-b1f571873850]
>  with start_ jobs being triggers needed manual approval for starting the 
> actual jobs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to