You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by Stefan Podkowinski <sp...@apache.org> on 2017/11/27 12:05:22 UTC
CCM dependency in dtests
Just wanted to bring a recent discussion about how to use ccm from
dtests to your attention:
https://github.com/apache/cassandra-dtest/pull/13
Basically the idea is to not depend on a released ccm artifact, but to
use a dedicated git branch in the ccm repo instead for executing dtests.
Motivation and details can be found in the PR, please feel free to comment.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: CCM dependency in dtests
Posted by Stefan Podkowinski <sp...@apache.org>.
I did test run on b.a.o yesterday and looks like this isn't causing any
additional issues.
I've now merged the suggested change with dtest master.
Any updates to a new release or any hot fixes of the ccm dependency in
dtests will now have to happen by updating the test-branch in the ccm
repo (https://github.com/pcmanus/ccm/tree/cassandra-test). You can
simply open a PR for that. This will allow us to move ahead with ccm
fixes more quickly, without having to bug Philip each time to publish a
new release.
On 01.12.2017 00:06, Michael Kjellman wrote:
> Hey Stefan, any updates on this? Thanks.
>
> best,
> kjellman
>
>> On Nov 27, 2017, at 7:34 AM, Michael Kjellman <mk...@internalcircle.com> wrote:
>>
>> thanks for driving this Stefan.... this is definitely an issue that I recently saw too trying to get all the dtests passing. having logic you need to fix in 3 repos isn’t ideal at all.
>>
>>> On Nov 27, 2017, at 4:05 AM, Stefan Podkowinski <sp...@apache.org> wrote:
>>>
>>> Just wanted to bring a recent discussion about how to use ccm from
>>> dtests to your attention:
>>> https://github.com/apache/cassandra-dtest/pull/13
>>>
>>> Basically the idea is to not depend on a released ccm artifact, but to
>>> use a dedicated git branch in the ccm repo instead for executing dtests.
>>> Motivation and details can be found in the PR, please feel free to comment.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
>>> For additional commands, e-mail: dev-help@cassandra.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
>> For additional commands, e-mail: dev-help@cassandra.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: dev-help@cassandra.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: CCM dependency in dtests
Posted by Michael Kjellman <mk...@internalcircle.com>.
Hey Stefan, any updates on this? Thanks.
best,
kjellman
> On Nov 27, 2017, at 7:34 AM, Michael Kjellman <mk...@internalcircle.com> wrote:
>
> thanks for driving this Stefan.... this is definitely an issue that I recently saw too trying to get all the dtests passing. having logic you need to fix in 3 repos isn’t ideal at all.
>
>> On Nov 27, 2017, at 4:05 AM, Stefan Podkowinski <sp...@apache.org> wrote:
>>
>> Just wanted to bring a recent discussion about how to use ccm from
>> dtests to your attention:
>> https://github.com/apache/cassandra-dtest/pull/13
>>
>> Basically the idea is to not depend on a released ccm artifact, but to
>> use a dedicated git branch in the ccm repo instead for executing dtests.
>> Motivation and details can be found in the PR, please feel free to comment.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
>> For additional commands, e-mail: dev-help@cassandra.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: dev-help@cassandra.apache.org
>
Re: CCM dependency in dtests
Posted by Michael Kjellman <mk...@internalcircle.com>.
thanks for driving this Stefan.... this is definitely an issue that I recently saw too trying to get all the dtests passing. having logic you need to fix in 3 repos isn’t ideal at all.
> On Nov 27, 2017, at 4:05 AM, Stefan Podkowinski <sp...@apache.org> wrote:
>
> Just wanted to bring a recent discussion about how to use ccm from
> dtests to your attention:
> https://github.com/apache/cassandra-dtest/pull/13
>
> Basically the idea is to not depend on a released ccm artifact, but to
> use a dedicated git branch in the ccm repo instead for executing dtests.
> Motivation and details can be found in the PR, please feel free to comment.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: dev-help@cassandra.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org