[
https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501405#comment-17501405
]
Sam Tunnicliffe commented on CASSANDRA-17351:
---------------------------------------------
CCM isn't being updated in the container by {{pip3 install \-\-exists-action w
--upgrade \-r ~/cassandra-dtest/requirements.txt}} because although the sha
that the {{cassandra-test}} tag points at has been updated, the actual ccm
version in {{setup.py}} has not. Using the {{\-e/\-\-editable}} flag also
doesn't help beyond the short term as this causes pip to try and run a {{git
fetch \-q \-\-tags}} which will fail if there are local tags being overwritten
by remote ones. The workaround of specifying a custom dtest branch, which
includes the updated ccm in it's own {{requirements.txt}} works here because
the change to the dependency spec triggers a re-installation.
The solution is to bump the ccm version when retagging it. By doing this, pip
will do the upgrade as expected should there be changes since the container
image was built. I plan to push a change to ccm adding a {{.post1}} suffix to
the version and retagging it, at which point I expect the custom dtest/ccm
brach workaround to no longer be necessary.
> 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
