Date: Wed, 2 Jul 2014 17:39:26 -0700 From: Craig Rodrigues <rodrigc@FreeBSD.org> To: Julio Merino <jmmv@meroh.net> Cc: "freebsd-testing@freebsd.org" <freebsd-testing@freebsd.org>, "jenkins-admin@freebsd.org" <jenkins-admin@freebsd.org> Subject: Re: Kyua + Jenkins integration Message-ID: <CAG=rPVeuA3zA94E9-QW4oTQxiO-%2B5OFgdt%2B46SUssTu%2BynCZyQ@mail.gmail.com> In-Reply-To: <CAFY7cWAEQ=xVUiO4TGnnLy0yXdC5xaiOuyjACc01=_MXEMCOWA@mail.gmail.com> References: <CAG=rPVe136stcsGc5%2BURiHepfFbppwRL6NpmvVJMTWpkjGtxxQ@mail.gmail.com> <CAOtMX2iOP4nn=7St2uWXYNFcw4Lbru-P8M9sdPiWDD_sC3nBTA@mail.gmail.com> <CAFY7cWCa6xGfS3qG4-hHf2YwJLeEOvOXDp3Z5cXjRjjNtthenQ@mail.gmail.com> <CAG=rPVeamzKhh1J8FE258j00e=unfVzBN5bCJp9jAoHvz-S58g@mail.gmail.com> <CAFY7cWAEQ=xVUiO4TGnnLy0yXdC5xaiOuyjACc01=_MXEMCOWA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, OK, thanks for the explanation. It would be useful if the reporting options had a flag to direct output to a file: kyua report-junit -o foo.xml instead of: kyua report-junit > foo.xml However, without the "-o" flag, I can still live with it. Can you do another release of kyua with this change, and maybe Garrett's TAP fixes? What you have done is very useful, and I want to deploy it on multiple machines via "pkg install" instead of downloading the source and building it myself. Thanks. -- Craig On Fri, Jun 27, 2014 at 8:44 AM, Julio Merino <jmmv@meroh.net> wrote: > On Mon, Jun 16, 2014 at 4:59 PM, Craig Rodrigues <rodrigc@freebsd.org> > wrote: > > On Wed, Jun 11, 2014 at 3:23 AM, Julio Merino <jmmv@meroh.net> wrote: > >> > >> > https://github.com/jmmv/kyua/commit/7acd1a1fa05e600ac41094857ee1344f4ae7adb5 > >> > > > > By default, "kyua report-html" will write output files in the ./html > directory, > > unless overridden by "--output [directory]". > > However, "kyua report-junit" seems to write output files to stdout > > instead by default. > > > > You might want to make the default behavior of "kyua report-junit" by > closer > > to "kyua report-html", i.e. do not write the output files to stdout by > default. > > This is intentional and is part of the reason why every output format > has its own command: their behaviors are different and attempting to > represent them with the same command-line interface would be more > confusing. The HTML output generates more than one file so it cannot > write to stdout. But that's the exception, not the norm: both report > and report-junit generate single files and print them to stdout. > > The plan is to make report-html write a single file by default (with > an option for chunked output) and write that to stdout. Other than for > consistency reasons, this would resolve some of the concerns with the > current HTML output (aka harder to manage than atf's due to the > multi-file setup.) >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG=rPVeuA3zA94E9-QW4oTQxiO-%2B5OFgdt%2B46SUssTu%2BynCZyQ>