You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@bigtop.apache.org by Martin Bukatovic <mb...@redhat.com> on 2013/07/19 16:25:40 UTC
old information in README file
Dear all,
I have noticed that in README file inside bigtop repository, the text uses old
and deprecated filepaths:
> * install package testing iTest artifacts locally:
>
> cd test/src/smokes/package/ && mvn install -DskipTests -DskipITs -DperformRelease
>
> * use those locally installed iTest package testing artifacts to run a suite:
>
> cd test/suites/package/ && mvn clean verify -Dbigtop.repo.file.url.CentOS=XXX -D'org.apache.maven-failsafe-plugin.testInclude=**/TestPackagesReadiness.*'
The repo was restructured quite time ago, and I guess that the instructions
should eg. read bigtop-tests/test-execution/smokes instead of
test/src/smokes/package and test/suites/package (but I'm not sure about the
second one).
Please review the README and possibly fix it.
Also there are correct instructions on the wiki, so maybe it may be merged or
referenced instead:
https://cwiki.apache.org/confluence/display/BIGTOP/Running+integration+and+system+tests
Thank you
Martin Bukatovic
Re: old information in README file
Posted by Jay Vyas <ja...@gmail.com>.
Here's my attempt at a patch :) I think this will make it alot easier for
newcomers
https://issues.apache.org/jira/secure/attachment/12593243/README.patch
On Fri, Jul 19, 2013 at 2:39 PM, Sean Mackrory <ma...@gmail.com> wrote:
> Not a PMC member, but unless you're pushing your feature branches no
> one else is going to see them, so you can just do what works best for
> you. You can also specify a range of commits to include in your patch.
> e.g.
>
> git format-patch origin/master..master
>
> On Fri, Jul 19, 2013 at 11:09 AM, Lewis John Mcgibbney
> <le...@gmail.com> wrote:
> > Anyone is able to open a ticket in the Bigtop Jira here [0]. You will
> need
> > to sign up for a username as as on the wiki.
> > The rule of thumb here is to make an attempt to check if a similar
> ticket is
> > already open before opening new tickets.
> > You can make the changes to the Bigtop trunk code and generate a patch as
> > follows
> >
> > //make a new branch
> > git checkout -b $ISSUE_NUMBER
> > //make local changes and commit them
> > git format-patch master --stdout > $ISSUE_NUMBER.patch
> >
> > Apply your patch to the issue you created in Jira. Folks can then apply
> your
> > patch and run with it.
> >
> > I would like for some Bigtop PMC's to jump in here as maybe a feature
> branch
> > for every patch is a bit of an overkill.
> >
> > hth
> >
> > [0] https://issues.apache.org/jira/browse/BIGTOP
> >
> >
> > On Fri, Jul 19, 2013 at 8:51 AM, Jay Vyas <ja...@gmail.com> wrote:
> >>
> >> How can we apply this patch? I had some other updates for the readme as
> >> well.. Sorry for the ignorance.
> >>
> >>
> >> On Fri, Jul 19, 2013 at 11:14 AM, Lewis John Mcgibbney
> >> <le...@gmail.com> wrote:
> >>>
> >>> Hi Martin,
> >>> Do you use bigtop trunk?
> >>> If so are you able to patch bigtop and file a Jira ticket?
> >>> Thanks
> >>> Lewis
> >>>
> >>>
> >>> On Friday, July 19, 2013, Martin Bukatovic <mb...@redhat.com>
> wrote:
> >>> > Dear all,
> >>> >
> >>> > I have noticed that in README file inside bigtop repository, the text
> >>> > uses old
> >>> > and deprecated filepaths:
> >>> >
> >>> >> * install package testing iTest artifacts locally:
> >>> >>
> >>> >> cd test/src/smokes/package/ && mvn install -DskipTests
> >>> >> -DskipITs -DperformRelease
> >>> >>
> >>> >> * use those locally installed iTest package testing artifacts to
> run a
> >>> >> suite:
> >>> >>
> >>> >> cd test/suites/package/ && mvn clean verify
> >>> >> -Dbigtop.repo.file.url.CentOS=XXX
> >>> >>
> -D'org.apache.maven-failsafe-plugin.testInclude=**/TestPackagesReadiness.*'
> >>> >
> >>> > The repo was restructured quite time ago, and I guess that the
> >>> > instructions
> >>> > should eg. read bigtop-tests/test-execution/smokes instead of
> >>> > test/src/smokes/package and test/suites/package (but I'm not sure
> about
> >>> > the
> >>> > second one).
> >>> >
> >>> > Please review the README and possibly fix it.
> >>> >
> >>> > Also there are correct instructions on the wiki, so maybe it may be
> >>> > merged or
> >>> > referenced instead:
> >>> >
> >>> >
> >>> >
> https://cwiki.apache.org/confluence/display/BIGTOP/Running+integration+and+system+tests
> >>> >
> >>> > Thank you
> >>> >
> >>> > Martin Bukatovic
> >>> >
> >>>
> >>> --
> >>> Lewis
> >>>
> >>
> >>
> >>
> >> --
> >> Jay Vyas
> >> http://jayunit100.blogspot.com
> >
> >
> >
> >
> > --
> > Lewis
>
--
Jay Vyas
http://jayunit100.blogspot.com
Re: old information in README file
Posted by Sean Mackrory <ma...@gmail.com>.
Not a PMC member, but unless you're pushing your feature branches no
one else is going to see them, so you can just do what works best for
you. You can also specify a range of commits to include in your patch.
e.g.
git format-patch origin/master..master
On Fri, Jul 19, 2013 at 11:09 AM, Lewis John Mcgibbney
<le...@gmail.com> wrote:
> Anyone is able to open a ticket in the Bigtop Jira here [0]. You will need
> to sign up for a username as as on the wiki.
> The rule of thumb here is to make an attempt to check if a similar ticket is
> already open before opening new tickets.
> You can make the changes to the Bigtop trunk code and generate a patch as
> follows
>
> //make a new branch
> git checkout -b $ISSUE_NUMBER
> //make local changes and commit them
> git format-patch master --stdout > $ISSUE_NUMBER.patch
>
> Apply your patch to the issue you created in Jira. Folks can then apply your
> patch and run with it.
>
> I would like for some Bigtop PMC's to jump in here as maybe a feature branch
> for every patch is a bit of an overkill.
>
> hth
>
> [0] https://issues.apache.org/jira/browse/BIGTOP
>
>
> On Fri, Jul 19, 2013 at 8:51 AM, Jay Vyas <ja...@gmail.com> wrote:
>>
>> How can we apply this patch? I had some other updates for the readme as
>> well.. Sorry for the ignorance.
>>
>>
>> On Fri, Jul 19, 2013 at 11:14 AM, Lewis John Mcgibbney
>> <le...@gmail.com> wrote:
>>>
>>> Hi Martin,
>>> Do you use bigtop trunk?
>>> If so are you able to patch bigtop and file a Jira ticket?
>>> Thanks
>>> Lewis
>>>
>>>
>>> On Friday, July 19, 2013, Martin Bukatovic <mb...@redhat.com> wrote:
>>> > Dear all,
>>> >
>>> > I have noticed that in README file inside bigtop repository, the text
>>> > uses old
>>> > and deprecated filepaths:
>>> >
>>> >> * install package testing iTest artifacts locally:
>>> >>
>>> >> cd test/src/smokes/package/ && mvn install -DskipTests
>>> >> -DskipITs -DperformRelease
>>> >>
>>> >> * use those locally installed iTest package testing artifacts to run a
>>> >> suite:
>>> >>
>>> >> cd test/suites/package/ && mvn clean verify
>>> >> -Dbigtop.repo.file.url.CentOS=XXX
>>> >> -D'org.apache.maven-failsafe-plugin.testInclude=**/TestPackagesReadiness.*'
>>> >
>>> > The repo was restructured quite time ago, and I guess that the
>>> > instructions
>>> > should eg. read bigtop-tests/test-execution/smokes instead of
>>> > test/src/smokes/package and test/suites/package (but I'm not sure about
>>> > the
>>> > second one).
>>> >
>>> > Please review the README and possibly fix it.
>>> >
>>> > Also there are correct instructions on the wiki, so maybe it may be
>>> > merged or
>>> > referenced instead:
>>> >
>>> >
>>> > https://cwiki.apache.org/confluence/display/BIGTOP/Running+integration+and+system+tests
>>> >
>>> > Thank you
>>> >
>>> > Martin Bukatovic
>>> >
>>>
>>> --
>>> Lewis
>>>
>>
>>
>>
>> --
>> Jay Vyas
>> http://jayunit100.blogspot.com
>
>
>
>
> --
> Lewis
Re: old information in README file
Posted by Lewis John Mcgibbney <le...@gmail.com>.
Anyone is able to open a ticket in the Bigtop Jira here [0]. You will need
to sign up for a username as as on the wiki.
The rule of thumb here is to make an attempt to check if a similar ticket
is already open before opening new tickets.
You can make the changes to the Bigtop trunk code and generate a patch as
follows
//make a new branch
git checkout -b $ISSUE_NUMBER
//make local changes and commit them
git format-patch master --stdout > $ISSUE_NUMBER.patch
Apply your patch to the issue you created in Jira. Folks can then apply
your patch and run with it.
I would like for some Bigtop PMC's to jump in here as maybe a feature
branch for every patch is a bit of an overkill.
hth
[0] https://issues.apache.org/jira/browse/BIGTOP
On Fri, Jul 19, 2013 at 8:51 AM, Jay Vyas <ja...@gmail.com> wrote:
> How can we apply this patch? I had some other updates for the readme as
> well.. Sorry for the ignorance.
>
>
> On Fri, Jul 19, 2013 at 11:14 AM, Lewis John Mcgibbney <
> lewis.mcgibbney@gmail.com> wrote:
>
>> Hi Martin,
>> Do you use bigtop trunk?
>> If so are you able to patch bigtop and file a Jira ticket?
>> Thanks
>> Lewis
>>
>>
>> On Friday, July 19, 2013, Martin Bukatovic <mb...@redhat.com> wrote:
>> > Dear all,
>> >
>> > I have noticed that in README file inside bigtop repository, the text
>> uses old
>> > and deprecated filepaths:
>> >
>> >> * install package testing iTest artifacts locally:
>> >>
>> >> cd test/src/smokes/package/ && mvn install -DskipTests
>> -DskipITs -DperformRelease
>> >>
>> >> * use those locally installed iTest package testing artifacts to run a
>> suite:
>> >>
>> >> cd test/suites/package/ && mvn clean verify
>> -Dbigtop.repo.file.url.CentOS=XXX
>> -D'org.apache.maven-failsafe-plugin.testInclude=**/TestPackagesReadiness.*'
>> >
>> > The repo was restructured quite time ago, and I guess that the
>> instructions
>> > should eg. read bigtop-tests/test-execution/smokes instead of
>> > test/src/smokes/package and test/suites/package (but I'm not sure about
>> the
>> > second one).
>> >
>> > Please review the README and possibly fix it.
>> >
>> > Also there are correct instructions on the wiki, so maybe it may be
>> merged or
>> > referenced instead:
>> >
>> >
>> https://cwiki.apache.org/confluence/display/BIGTOP/Running+integration+and+system+tests
>> >
>> > Thank you
>> >
>> > Martin Bukatovic
>> >
>>
>> --
>> *Lewis*
>>
>>
>
>
> --
> Jay Vyas
> http://jayunit100.blogspot.com
>
--
*Lewis*
Re: old information in README file
Posted by Jay Vyas <ja...@gmail.com>.
How can we apply this patch? I had some other updates for the readme as
well.. Sorry for the ignorance.
On Fri, Jul 19, 2013 at 11:14 AM, Lewis John Mcgibbney <
lewis.mcgibbney@gmail.com> wrote:
> Hi Martin,
> Do you use bigtop trunk?
> If so are you able to patch bigtop and file a Jira ticket?
> Thanks
> Lewis
>
>
> On Friday, July 19, 2013, Martin Bukatovic <mb...@redhat.com> wrote:
> > Dear all,
> >
> > I have noticed that in README file inside bigtop repository, the text
> uses old
> > and deprecated filepaths:
> >
> >> * install package testing iTest artifacts locally:
> >>
> >> cd test/src/smokes/package/ && mvn install -DskipTests
> -DskipITs -DperformRelease
> >>
> >> * use those locally installed iTest package testing artifacts to run a
> suite:
> >>
> >> cd test/suites/package/ && mvn clean verify
> -Dbigtop.repo.file.url.CentOS=XXX
> -D'org.apache.maven-failsafe-plugin.testInclude=**/TestPackagesReadiness.*'
> >
> > The repo was restructured quite time ago, and I guess that the
> instructions
> > should eg. read bigtop-tests/test-execution/smokes instead of
> > test/src/smokes/package and test/suites/package (but I'm not sure about
> the
> > second one).
> >
> > Please review the README and possibly fix it.
> >
> > Also there are correct instructions on the wiki, so maybe it may be
> merged or
> > referenced instead:
> >
> >
> https://cwiki.apache.org/confluence/display/BIGTOP/Running+integration+and+system+tests
> >
> > Thank you
> >
> > Martin Bukatovic
> >
>
> --
> *Lewis*
>
>
--
Jay Vyas
http://jayunit100.blogspot.com
Re: old information in README file
Posted by Lewis John Mcgibbney <le...@gmail.com>.
Hi Martin,
Do you use bigtop trunk?
If so are you able to patch bigtop and file a Jira ticket?
Thanks
Lewis
On Friday, July 19, 2013, Martin Bukatovic <mb...@redhat.com> wrote:
> Dear all,
>
> I have noticed that in README file inside bigtop repository, the text
uses old
> and deprecated filepaths:
>
>> * install package testing iTest artifacts locally:
>>
>> cd test/src/smokes/package/ && mvn install -DskipTests -DskipITs
-DperformRelease
>>
>> * use those locally installed iTest package testing artifacts to run a
suite:
>>
>> cd test/suites/package/ && mvn clean verify
-Dbigtop.repo.file.url.CentOS=XXX
-D'org.apache.maven-failsafe-plugin.testInclude=**/TestPackagesReadiness.*'
>
> The repo was restructured quite time ago, and I guess that the
instructions
> should eg. read bigtop-tests/test-execution/smokes instead of
> test/src/smokes/package and test/suites/package (but I'm not sure about
the
> second one).
>
> Please review the README and possibly fix it.
>
> Also there are correct instructions on the wiki, so maybe it may be
merged or
> referenced instead:
>
>
https://cwiki.apache.org/confluence/display/BIGTOP/Running+integration+and+system+tests
>
> Thank you
>
> Martin Bukatovic
>
--
*Lewis*