[
https://issues.apache.org/jira/browse/CASSANDRA-17182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17482319#comment-17482319
]
Michael Semb Wever commented on CASSANDRA-17182:
------------------------------------------------
bq. Michael Semb Wever that I did but I wasn't sure about the staging and
commit part after that as you mentioned before there are some steps you still
work on if I am not mistaken.
If you followed those steps to test, then merge to trunk.
[ci-cassandra.apache.org|https://ci-cassandra.apache.org/job/cassandra-website/]
will then automatically (CD) it to https://cassandra.staged.apache.org .
Once you have verified it (and all new changes) on cassandra.staged.apache.org
then do
{code}
git fetch origin
git switch asf-site
git reset --hard origin/asf-staging
git push -f origin asf-site
{code}
as described
[here|https://github.com/apache/cassandra-website#merging-asf-staging-to-asf-site].
> 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]
