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

Ekaterina Dimitrova commented on CASSANDRA-17182:
-------------------------------------------------

{quote}For new things that can't be tied to a release just use the NA version.
{quote}
Exactly, as far as I know we don't add all versions when we commit to dtest or 
anywhere else where the change will affect by default all versions. 
{quote}Are my eyes fooling me or is {{-e}} missing in the given example?
{quote}
Check again :D This mistake proved exactly what I said we need to skip - having 
to update at more than one place. So what happened - I had the wrong (without 
-e) example in the ticket description, I used it in the commit and then noticed 
I have to correct the ticket but forgot I copy-pasted that line in the commit. 
:) 

> Add info how to test with your own CCM branch
> ---------------------------------------------
>
>                 Key: CASSANDRA-17182
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17182
>             Project: Cassandra
>          Issue Type: Task
>          Components: Documentation/Website
>            Reporter: Ekaterina Dimitrova
>            Assignee: Ekaterina Dimitrova
>            Priority: Low
>
> In CASSANDRA-16688 we solved an issue with ccm and retagging.
> It required to remove the -e from the beginning of [this 
> row|https://github.com/apache/cassandra-dtest/blob/trunk/requirements.txt#L9]
> But now if someone wants to test with their own ccm branch, they need to add 
> back the -e during testing so that pip3 updates with their branch. Without 
> it, it doesn't update.
> *Example:*
> {code:java}
> -e git+https://github.com/riptano/ccm.git@cassandra-test#egg=ccm
> {code}
> This is important information and I think we need to add it to at least:
>  - our Testing page where dtest runs are mentioned on the website
>  - Add a comment in requirements.txt in the dtest repo
> We can also update the README files of CCM and DTests but then if something 
> changes we will need to update this info in 4 places which doesn't seem 
> efficient to me.



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

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

Reply via email to