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

Ekaterina Dimitrova commented on CASSANDRA-16489:
-------------------------------------------------

I ended up running CI as I was trying to fix one more issue which we thought it 
is a matter of line but it turned out it is not so I am going to open a new 
ticket for that one.

 CI runs look similar to Jenkins:
MIDRES - [JAVA8 | 
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/668/workflows/fdc790c1-86ed-4132-9bd7-8f514e7d9574]
 | [JAVA11 | 
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/667/workflows/ace464c4-41eb-4ca5-8814-508e130a88b1]
HIGHRES - [JAVA8 | 
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/668/workflows/fdc790c1-86ed-4132-9bd7-8f514e7d9574]
 | [JAVA11 
|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/668/workflows/6f361605-0da3-40e3-ba49-fd9eb0c6d324
 ]

> Add utest_system_keyspace_directory to CircleCI config template
> ---------------------------------------------------------------
>
>                 Key: CASSANDRA-16489
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16489
>             Project: Cassandra
>          Issue Type: Bug
>          Components: CI
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>            Priority: Normal
>             Fix For: 4.0, 4.0-beta
>
>
> In CASSANDRA-14793 a new circle job config was added directly to the CircleCI 
> base, LOWRES, MIDRES and HIGHRES config files, but not to the template file. 
> When the config was regenerated for CASSANDRA-16474, the new job was lost. We 
> should restore it and add it to the config template to avoid any reoccurrence.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to