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

Ekaterina Dimitrova commented on CASSANDRA-17351:
-------------------------------------------------

On my end, I confirmed with the people who maintain the drivers at the moment 
that this change does not affect them. We need probably to make a new release 
of ccm soon, but that is another topic for a different ticket. CC 
[~absurdfarce] 
{quote}While we're here, should we sync the docker images used by the various 
circle jobs? I've tried a run against trunk using the {{20210929}} image for 
everything, and I only see a couple of test failures (both with JIRAs already)
{quote}
I also noticed the different image. I also wanted to suggest we add "latest" 
tag instead of explicit date, that's what we also do in Jenkins. This can save 
us time and efforts when we build a new image to update all branches Circle CI 
config. If for some reason sometimes we want to use workaround temporarily, 
then we can always change to specific image by date. What do others think? 

 

 

> Pip doesn't install ccm every time
> ----------------------------------
>
>                 Key: CASSANDRA-17351
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17351
>             Project: Cassandra
>          Issue Type: Task
>          Components: CI
>            Reporter: Ekaterina Dimitrova
>            Assignee: Ekaterina Dimitrova
>            Priority: Urgent
>             Fix For: 4.x
>
>
> In CASSANDRA-16688 we fixed requirements.txt in DTest repo, pip install to 
> run without -e for ccm in order to address the moveable tag. That worked for 
> some time until last night. I successfully retagged and now ccm is not 
> re-installed in Circle CI.
> Jenkins picked stuff though. But it was acting unreliably and weird so 
> rerunning now things there. Results pending.
> Now I added -e for ccm in requirements.txt and it worked in CircleCI. Still 
> pending results. I don't think this will be permanent solution and I am not 
> sure whether it will affect also the previous branches in a way. We need to 
> further investigate it and test. 
> For now I will ask people to test with -e until we figure it out.
> CC [~mck] , [~bereng] , [~dcapwell]  and [~stefan.miklosovic] 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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

Reply via email to