Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 10 Jun 2014 21:44:30 -0600
From:      Alan Somers <asomers@freebsd.org>
To:        Craig Rodrigues <rodrigc@freebsd.org>
Cc:        "freebsd-testing@freebsd.org" <freebsd-testing@freebsd.org>, "jenkins-admin@freebsd.org" <jenkins-admin@freebsd.org>
Subject:   Re: Kyua + Jenkins integration
Message-ID:  <CAOtMX2iOP4nn=7St2uWXYNFcw4Lbru-P8M9sdPiWDD_sC3nBTA@mail.gmail.com>
In-Reply-To: <CAG=rPVe136stcsGc5%2BURiHepfFbppwRL6NpmvVJMTWpkjGtxxQ@mail.gmail.com>
References:  <CAG=rPVe136stcsGc5%2BURiHepfFbppwRL6NpmvVJMTWpkjGtxxQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 10, 2014 at 7:49 PM, Craig Rodrigues <rodrigc@freebsd.org> wrote:
> Hi,
>
> At BSDCan 2014, I met with Julio Merino,
> and we discussed how we could better integrate Kyua and Jenkins.
>
> To summarize, Julio modified Kyua, so that someone can do:
>
> kyua test        (runs the tests)
> kyua report-junit     (creates test output in JUnit XML format)
>
> The JUnit XML can be directly imported into Jenkins,
> which has a UI for reporting the status of tests.
>
> I ran the Kyua tests in the /usr/tests directory in FreeBSD
> and imported the output into Jenkins here:
>
> https://jenkins.freebsd.org/jenkins/job/Kyua_Integration/5/testReport/
>
>
> This is a significant milestone!
> We will definitely build on this moving forward
>
> Thanks to Julio for working on the code, and blogging about it here:
>
> http://julipedia.meroh.net/2014/05/refocusing-kyua-maybe.html
>
> --
> Craig
> _______________________________________________
> freebsd-testing@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-testing
> To unsubscribe, send any mail to "freebsd-testing-unsubscribe@freebsd.org"

Nice!  Also, the "diff" columns will be very useful, if they do what I
think they do.  But I do see one problem: there's no message for why a
test was skipped.  Plain "kyua report" will give an explanation like
"skipped: required configuration variable Foo was undefined".  But
that doesn't show up in the Jenkins output.

-Alan



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2iOP4nn=7St2uWXYNFcw4Lbru-P8M9sdPiWDD_sC3nBTA>