Date: Sat, 15 Nov 2014 19:54:30 -0800 From: Craig Rodrigues <rodrigc@FreeBSD.org> To: Warren Block <wblock@wonkity.com> Cc: "freebsd-testing@freebsd.org" <freebsd-testing@freebsd.org> Subject: Re: Documentation testing and textproc/igor Message-ID: <CAG=rPVc2me%2B5vOcRfcC9-dB_AZSmmaC3APQdyQLS3b3u3ZJyrQ@mail.gmail.com> In-Reply-To: <alpine.BSF.2.11.1411151919590.24432@wonkity.com> References: <alpine.BSF.2.11.1411151919590.24432@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- Craig
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG=rPVc2me%2B5vOcRfcC9-dB_AZSmmaC3APQdyQLS3b3u3ZJyrQ>