karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jamie G." <jamie.goody...@gmail.com>
Subject Re: [PROPOSAL] Add run-it profile and enable on Jenkins
Date Wed, 05 Mar 2014 12:07:44 GMT
Being able to skip itests would be good from my Point of View - often
during RC builds an itest will randomly fail, causing a step to be
reissued. I'd still want my Jenkins builds to be running all tests
however by default.

--Jamie

On Wed, Mar 5, 2014 at 7:40 AM, Jean-Baptiste Onofré <jb@nanthrax.net> wrote:
> Allright guys. I follow you.
>
> In that case, I'm cleaning the pom, fixing and enabling tooling itests by
> default.
>
> Thanks
> Regards
> JB
>
>
> On 03/05/2014 11:30 AM, Achim Nierbeck wrote:
>>
>> Hi,
>>
>> I'd rather skipt integration tests per usage, cause at this point I'm in
>> charge and should know what I do ;)
>> That's why I object on disabling the itests per default.
>>
>> regards, Achim
>>
>>
>> 2014-03-05 10:16 GMT+01:00 jb@nanthrax.net <jb@nanthrax.net>:
>>
>>> The only drawback is that itests consume resources and take times.
>>>
>>> I'm ok to enable it by default (I will fix in tooling as it's not the
>>> case
>>> for now).
>>>
>>> Let see the feedback from the others.
>>>
>>> Regards
>>> JB
>>> --
>>> Jean-Baptiste Onofré
>>> jbonofre@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://wwx.talend.com
>>>
>>> ----- Reply message -----
>>> From: "Christian Schneider" <chris@die-schneider.net>
>>> To: <dev@karaf.apache.org>
>>> Subject: [PROPOSAL] Add run-it profile and enable on Jenkins
>>> Date: Wed, Mar 5, 2014 9:59 am
>>>
>>>
>>> I think the tests are currently fast enough to run by default.
>>> Having a default to not run itests often tends to let people skip itests
>>> before a commit.
>>> In the end it is just a question of default as we currently also can
>>> skip the itests but I think
>>> the default of running the itests communicates that they are important
>>> to us.
>>>
>>> Christian
>>>
>>> On 05.03.2014 09:45, Jean-Baptiste Onofré wrote:
>>>>
>>>> Hi all,
>>>>
>>>> Right now, our itests are always run when you build with a simple mvn
>>>> clean install.
>>>>
>>>> I would like to propose:
>>>> - create a itests profile in itests and tooling (renaming of
>>>> ci-build-profile as it's not related to ci only)
>>>> - enable the run-it profile on Jenkins by default
>>>> - document the usage of this new profile
>>>>
>>>> It means that:
>>>> - mvn clean install will execute all utests, but not itests by default
>>>> - mvn clean install -Pitests will execute all utests, and itests
>>>> - mvn clean install -DskipTests will not execute utests, neither itests
>>>> - mvn clean install -DskipTests -Pitests will not execute utests, but
>>>> itests will be executed
>>>>
>>>> WDYT ?
>>>>
>>>> Regards
>>>> JB
>>>
>>>
>>>
>>> --
>>> Christian Schneider
>>> http://www.liquid-reality.de
>>>
>>> Open Source Architect
>>> http://www.talend.com
>>>
>>>
>>
>>
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com

Mime
View raw message