Date: Sun, 16 Nov 2014 08:21:55 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: Craig Rodrigues <rodrigc@FreeBSD.org> Cc: "freebsd-testing@freebsd.org" <freebsd-testing@freebsd.org> Subject: Re: Documentation testing and textproc/igor Message-ID: <alpine.BSF.2.11.1411160820100.93232@wonkity.com> In-Reply-To: <CAG=rPVc2me%2B5vOcRfcC9-dB_AZSmmaC3APQdyQLS3b3u3ZJyrQ@mail.gmail.com> References: <alpine.BSF.2.11.1411151919590.24432@wonkity.com> <CAG=rPVc2me%2B5vOcRfcC9-dB_AZSmmaC3APQdyQLS3b3u3ZJyrQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 15 Nov 2014, Craig Rodrigues wrote: > > > On Sat, Nov 15, 2014 at 6:29 PM, Warren Block <wblock@wonkity.com> wrote: > Since July, textproc/igor has a -X option that produces XML output. This should be usable with Jenkins for documentation testing. > > > I took a quick look at igor. Who told you that the XML output produced by igor is useful > for Jenkins documentation testing? The output looks like this: > > <file name="share/man/man8/rc.8"> > <error line="38" column="1" severity="warning" message="date not today, November 15, 2014" source="igor" /> > <error line="505" column="1" severity="warning" message="blank line" source="igor" /> > <error line="508" column="1" severity="warning" message="blank line" source="igor" /> > <error line="510" column="1" severity="warning" message="blank line" source="igor" /> > <error line="514" column="1" severity="warning" message="blank line" source="igor" /> > <error line="525" column="1" severity="warning" message="blank line" source="igor" /> > <error line="529" column="1" severity="warning" message="blank line" source="igor" /> > <error line="531" column="1" severity="warning" message="blank line" source="igor" /> > <error line="538" column="1" severity="warning" message="blank line" source="igor" /> > <error line="543" column="1" severity="warning" message="blank line" source="igor" /> > <error line="-" column="1" severity="warning" message="" source="igor" /> > </file> > > That output is not in JUnit XML format ( http://help.catchsoftware.com/display/ET/JUnit+Format ), so would need to be parsed by an additional > script in order to be used inside Jenkins. The current output is nice, but not useful on its own > for integration with Jenkins. The output it produces now is based on what lwhsu@ added at BSDCan. He showed a working demo there, so maybe additional wrappers were involved. It's also possible I've broken it in the meantime, too. From owner-freebsd-testing@FreeBSD.ORG Sun Nov 16 17:29:03 2014 Return-Path: <owner-freebsd-testing@FreeBSD.ORG> Delivered-To: freebsd-testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6CDE7409; Sun, 16 Nov 2014 17:29:03 +0000 (UTC) Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DF9E2FDB; Sun, 16 Nov 2014 17:29:02 +0000 (UTC) Received: by mail-la0-f47.google.com with SMTP id gq15so1495201lab.6 for <multiple recipients>; Sun, 16 Nov 2014 09:29:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=BVWiBaMjbOscR3PKyGysrZmwx+nnnA31nqExIIaBz80=; b=nQtgnPwhDO/ytYP1jGZHXOY+k2goZ+HtbMh0NAK3nSxv6PcozqJoSfBMPXkbJwP7/z LaJwmrSxAhgPUD9UVw30nad/1K6h8LH3U4vgSLO3hIsFkfdR1QlhiSXQ0CpjzcsoAMq4 7kepy0JKvqexOdOyG+T2KpBl3GjzqqC0J0QWuszFSrwidFLF1O1gglP83R6bepVz9G6+ o2+rGAKVaoHJDCaeD95KxIUXuogwmzoVPEAWb8w+h3fsvL1fUnxQSlNnngEHBAD2yJ83 clsYX55KK11zH/qXwSMXMrg60NcP1EXYTWyG/7NLoDEuRofUzJy9AazY1zvE22MQCbxO RcNQ== MIME-Version: 1.0 X-Received: by 10.152.36.201 with SMTP id s9mr21451919laj.17.1416158940578; Sun, 16 Nov 2014 09:29:00 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.130.168 with HTTP; Sun, 16 Nov 2014 09:29:00 -0800 (PST) In-Reply-To: <alpine.BSF.2.11.1411160820100.93232@wonkity.com> References: <alpine.BSF.2.11.1411151919590.24432@wonkity.com> <CAG=rPVc2me+5vOcRfcC9-dB_AZSmmaC3APQdyQLS3b3u3ZJyrQ@mail.gmail.com> <alpine.BSF.2.11.1411160820100.93232@wonkity.com> Date: Sun, 16 Nov 2014 09:29:00 -0800 X-Google-Sender-Auth: qYK-B9k72lplxLXqXvIfB7lM5dE Message-ID: <CAG=rPVdB6bgiX-riCwAvowsxGUBbstNpL8gqMzY_BV9KVam0hQ@mail.gmail.com> Subject: Re: Documentation testing and textproc/igor From: Craig Rodrigues <rodrigc@FreeBSD.org> To: Warren Block <wblock@wonkity.com>, Li-Wen Hsu <lwhsu@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-testing@freebsd.org" <freebsd-testing@freebsd.org> X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Testing on FreeBSD <freebsd-testing.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-testing>, <mailto:freebsd-testing-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-testing/>; List-Post: <mailto:freebsd-testing@freebsd.org> List-Help: <mailto:freebsd-testing-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-testing>, <mailto:freebsd-testing-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sun, 16 Nov 2014 17:29:03 -0000 On Sun, Nov 16, 2014 at 7:21 AM, Warren Block <wblock@wonkity.com> wrote: > > The output it produces now is based on what lwhsu@ added at BSDCan. He > showed a working demo there, so maybe additional wrappers were involved. > It's also possible I've broken it in the meantime, too. Li-Wen, do you have the wrappers to parse the output of igor? Can you hand off this work to somone else, maybe in the freebsd-doc team to complete? You are doing very good work on maintaining the devel/jenkins port, but I don't like how you are starting Jenkins FreeBSD work items, and not following them to completion. We need to pull in more volunteers to keep things going, but we need people who are going to finish things that they start, and not leave things half done. -- Craig
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.11.1411160820100.93232>