You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by Aleksandr Sorokoumov <al...@gmail.com> on 2017/02/07 09:23:37 UTC
dtest commit id in CI builds
Hello,
I have been checking out recently some of the dtest-related issues and wanted to share an idea. It might be useful to see dtest’s commit id in the Jenkins logs. AFAIK Jenkins clones dtest master right now.
For example, it would be a bit easier to tackle some issues like CASSANDRA-13140 because one can immediately reproduce it with the same version of the dtest used in the build and after that reason about the changes between this revision and the master using git history for the particular test.
What do you think?
—
Best regards,
Aleksandr Sorokoumov
Re: dtest commit id in CI builds
Posted by Michael Shuler <mi...@pbandjelly.org>.
(sorry for previous blank reply..)
Please create a JIRA and it can be assigned to me. `mshuler` is my JIRA
user.
--
Kind regards,
Michael
On 02/07/2017 03:23 AM, Aleksandr Sorokoumov wrote:
> Hello,
>
> I have been checking out recently some of the dtest-related issues
> and wanted to share an idea. It might be useful to see dtest\u2019s commit
> id in the Jenkins logs. AFAIK Jenkins clones dtest master right now.
> For example, it would be a bit easier to tackle some issues like
> CASSANDRA-13140 because one can immediately reproduce it with the
> same version of the dtest used in the build and after that reason
> about the changes between this revision and the master using git
> history for the particular test.
>
> What do you think?
>
> \u2014 Best regards, Aleksandr Sorokoumov
>
Re: dtest commit id in CI builds
Posted by Michael Shuler <mi...@pbandjelly.org>.
On 02/07/2017 03:23 AM, Aleksandr Sorokoumov wrote:
> Hello,
>
> I have been checking out recently some of the dtest-related issues and wanted to share an idea. It might be useful to see dtest\u2019s commit id in the Jenkins logs. AFAIK Jenkins clones dtest master right now.
> For example, it would be a bit easier to tackle some issues like CASSANDRA-13140 because one can immediately reproduce it with the same version of the dtest used in the build and after that reason about the changes between this revision and the master using git history for the particular test.
>
> What do you think?
>
> \u2014
> Best regards,
> Aleksandr Sorokoumov
>