If it's helpful, I'd be happy to send you, off-list, the XML configuration file (which is Jenkins' serialized format) and/or screenshots of any of our jobs. It's a little bit of work because I have to make sure they're devoid of passwords and such.
Thanks! -- Philip On Wed, Jul 11, 2018 at 8:16 AM Michael Brown <[email protected]> wrote: > That's just the standard Jenkins plugin to read Junit XML. I think it comes > with a standard Jenkins install on Ubuntu 16. > > https://plugins.jenkins.io/junit > > Most of our tests already emit Junit XML, so that's taken care of for you > already. > > To use the plugin, you just tell it a series of paths to find find Junit > XML. For ubuntu-16.04-from-scratch, it's "Impala/logs_static/**/*.xml". > > > > On Tue, Jul 10, 2018 at 7:19 PM, Quanlong Huang <[email protected]> > wrote: > > > Thank you, Jim! That's really helpful! > > > > > > Could you share more about the fancy test report page? For example, > > https://jenkins.impala.io/job/ubuntu-16.04-from-scratch/ > > lastCompletedBuild/testReport/ > > > > > > I think you may have spent some time integrating the Jenkins Test Results > > plugin with the Impala test framework. It would save us most efforts if > you > > can share something about it. > > > > > > Thanks, > > Quanlong > > At 2018-07-10 23:40:26, "Jim Apple" <[email protected]> > wrote: > > >side note: please change the subject line for new topics; it will help > > >organize inboxes and list archives. > > > > > >The Jenkins jobs mostly use components in the repo. In particular, the > > >following scrips are each used in one of our core Jenkins jobs: > > > > > >bin/bootstrap_development.sh > > > > > >bin/bootstrap_build.sh > > > > > >bin/check-rat-report.py > > > > > >docs/Makefile > > > > > >bin/run_clang_tidy.sh > > > > > >bin/jenkins/build-all-flag-combinations.sh > > > > > >The only one that's used in a non-obvious way is the clang tidy script. > It > > >is used as follows: > > > > > >./bin/clean.sh > > >TIDY_BUILD_OUT="${WORKSPACE}/tidylog.txt" > > >touch "${TIDY_BUILD_OUT}" > > >if ! ./buildall.sh -skiptests -tidy -so -noclean &>"${TIDY_BUILD_OUT}" > > >then > > > echo "tidy build failed; See ${TIDY_BUILD_OUT} for full tidy build > > >output. Guess:" > > > grep ': error: ' "${TIDY_BUILD_OUT}" > > > exit 1 > > >else > > > ./bin/clean.sh > > > bin/run_clang_tidy.sh &>"${TIDY_BUILD_OUT}" > > > ! grep ']' "${TIDY_BUILD_OUT}" > > >fi > > > > > > > > >On Mon, Jul 9, 2018 at 8:36 PM, Quanlong Huang <[email protected]> > > >wrote: > > > > > >> Hi Lars, though not directly relate to this topic, we'd like to set-up > > >> testing like the community Jenkins. > > >> > > >> > > >> Are the jenkins scripts open-source? Could you share the configures of > > the > > >> Jenkins jobs? Looks like they're not in the Impala repo. I'm unable to > > >> browse the configures of jobs in jenkins.impala.io since I can't > login. > > >
