On 8 August 2016 at 15:41, Ohad Levy wrote:
>
> On Mon, Aug 8, 2016 at 5:33 PM, Eric D Helms wrote:
>
>> This thread has seen a revival with many points being made on both sides.
>> However, things have gone cold for nearly a week now and there are
>>
On Mon, Aug 8, 2016 at 5:33 PM, Eric D Helms wrote:
> This thread has seen a revival with many points being made on both sides.
> However, things have gone cold for nearly a week now and there are
> processes and decisions that hinge on the outcome with respect to users and
This thread has seen a revival with many points being made on both sides.
However, things have gone cold for nearly a week now and there are
processes and decisions that hinge on the outcome with respect to users and
developers alike. Are we to assume that what has been done is done and this
The document you linked to sounds like they only integrate directly with a
handful of CI services but not Jenkins. It looks like they have a gem [1]
that would upload test coverage results but that won’t offload resources
from our Jenkins environment.
We have had code climate set up for a while
thanks
it is what i need.
On Monday, August 8, 2016 at 8:59:36 AM UTC+2, Dominic Cleal wrote:
>
> On 05/08/16 12:43, pronix pronix wrote:
> > hello
> > i want repeat some jenkins jobs on my own infrastructure.
> > where can i see setting for jenkins jobs? by default they are hidden.
> >
On 08/05, David Davis wrote:
> Thanks to Andrew we’re now generating a test coverage report in Jenkins for
> the katello on every PR and when code gets merged to master. We should be
> able to track our code coverage over time using these reports and hopefully
> it’ll improve our test coverage.
>
On 05/08/16 12:43, pronix pronix wrote:
> hello
> i want repeat some jenkins jobs on my own infrastructure.
> where can i see setting for jenkins jobs? by default they are hidden.
> thanks
Some are configured via Jenkins Job Builder with config files under