[jira] [Commented] (CASSANDRA-17182) Add info how to test with your own CCM branch

["Josh McKenzie (Jira)" <ji...@apache.org>]

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

Josh McKenzie commented on CASSANDRA-17182:
-------------------------------------------

I'll take review on this. I have a ticket that's been stalled on needing to do this for a bit anyway. :)

> 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}
> 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org