Hi Martin, I set it up as a separate job, notifying via Slack every success and failure. If we monitor this over the next weeks, this will give insight over possible discrepancies between the two test suites, I believe. I think this is more or less the same setup as it is on your Jenkins so I’d advocate for keeping yours as well for redundancy. Best Peter

Am 10.09.2021 um 17:13 schrieb Martin Holmes :

Thanks Peter! I hope it's a bit more maintainable than the original. Will this now run automatically as part of the regular build, so I can retire my Jenkins Test2 job?

Cheers, Martin

On 2021-09-10 12:22 a.m., Peter Stadler wrote:

...

Hi Martin and Council, at yesterday's Council meeting we decided to push your Test2 forward and run both test suites in parallel for some time to see whether they fail/succeed for the same issues. If this runs smooth, we might remove the original tests completely at some point. Syd was so kind to add a new „Test2“ target to the Makefile [1] and I set up a new job at the Paderborn Jenkins [2]. It simply runs `make clean test2` (so no artifacts are built). I had to update the `tei-log-parse-rules` and now everything seems to work nicely. Cheers Peter [1] https://github.com/TEIC/Stylesheets/commit/c8a8f6fbc0ff98c47041fc365a98f6d55... [2] https://jenkins.tei-c.org/job/Stylesheets-dev-Test2/

-- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre

I acknowledge and respect the lək̓ʷəŋən peoples on whose traditional territory the university stands and the Songhees, Esquimalt and WSÁNEĆ peoples whose historical relationships with the land continue to this day. _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council