[CASSANDRA-17351] Pip doesn't install ccm every time

• Type: Task
• Status: Resolved
• Priority: Urgent
• Resolution: Fixed
• Fix Version/s: 4.1-alpha1, 4.1
• Component/s: CI
• Change Category: Quality Assurance
• Complexity: Normal
• Platform: All

Source Control Link

https://github.com/riptano/ccm/commit/7e5ff6af02ac74c32c4380e1d1690b23e2a2c334

Test and Documentation Plan

 https://app.circleci.com/pipelines/github/beobal/cassandra?branch=cci%2Ftrunk&filter=all
 
Pipeline 386 was run when the tag pointed at dcce52eec82a912c3b799590229e332a42affd0b. If you drill into j8_separate_tests -> j8_cqlsh-dtests-py38-no-vnodes (or one of the other similar steps) -> Configure virtualenv and python Dependencies (edited) 

We can see this:

Resolved https://github.com/beobal/ccm.git
to commit dcce52eec82a912c3b799590229e332a42affd0b
...
Successfully installed cassandra-driver-3.24.0 ccm-3.1.6.dev1290...

Pipeline 387 was run after retagging, but without changing anything on the Cassandra, Circle or dtest side. Following the same path shows:

Resolved https://github.com/beobal/ccm.git
to commit 180f2879ffce121f102f26d16883693c01f3c9c8

...
Successfully installed cassandra-driver-3.24.0 ccm-3.1.6.dev1291...
so just moving the tag causes the version bump from 3.1.6.dev1290 to 3.1.6.dev1291

• Assignee: Ekaterina Dimitrova
• Reporter: Ekaterina Dimitrova

Authors

Michael Semb Wever, Sam Tunnicliffe

Reviewers

Ekaterina Dimitrova, Michael Semb Wever, Sam Tunnicliffe

• Created: 06/Feb/22 22:20
• Updated: 27/May/22 19:25
• Resolved: 11/Mar/22 12:17

Description

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