[
https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17491712#comment-17491712
]
Ekaterina Dimitrova commented on CASSANDRA-17351:
-------------------------------------------------
I made a new base image(only pushed to my personal docker hub account now) and
I did a quick test
[here|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1386/workflows/605e5f2d-33f4-4b33-b33b-a1069cb314c7/jobs/8968/steps]
which passed... (used the opportunity to add Java 17 so we it is available for
whoever want to play with it :) I personally do it, have some preliminary
circle config covering J8 and J17 for trunk where I clean issues)
Rebuilding now the second image and I can run full test later today to confirm
CI runs.
Changes I plan are:
* to start using latest tag and not particular one, the way we do it in
Jenkins.
* use the base image for the python tests as we do in Jenkins and the seconds
one for the rest of the jobs
* update requirements.txt that we need to rebuild image when retagging CCM
until we find different solution. In my mind just the -e etc usage has changed
with newer pip3 versions, I don't have different explanation. At the same time
they lack docs on that... At least I didn't find anything meaningful for now.
Happy to be proved wrong.
> 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: [email protected]
For additional commands, e-mail: [email protected]
