Re: [Tei-council] Jenkins builds failing and not failing

1 Feb 2021

      The errors we're seeing now, though, are from the Makefile; the nvdl 
stuff is run at line 191 and 192 of the Makefile, without any ant 
involvement. You can set failonerror on an ant call to exec, but the log 
parser is the only thing that will catch the Make stuff, I think.

I notice that the nvdl schema includes the old Schematron namespace:

<!-- foreign namespaces used in TEI -->
     <namespace ns="http://www.ascc.net/xml/schematron">
       <validate schema="schematron.rng"/>
       <attach useMode="allow"/>
     </namespace>

     <namespace ns="http://purl.oclc.org/dsdl/schematron">
       <validate schema="iso-schematron.rng"/>
       <attach useMode="allow"/>
     </namespace>

which we probably don't care about any more. I think it's a long time 
since anyone really looked at the nvdl.

Cheers,
Martin

On 2021-02-01 10:47 a.m., Peter Stadler wrote:
...
So, one more thing I just discovered (for myself):
This checkbox "Mark build Failed on Error“ does only apply to the log parsing. Usually, the ant task would fail, and the build would be flagged as failed by Jenkins. In this case, the ant script just goes on and we only find the errors in the log file.
So, it might not be bad to check this box but ideally the ant task should already fail.
Best
Peter
...
Am 01.02.2021 um 19:43 schrieb Martin Holmes :
They don't look like no-brainers to me. O Schematron Gurus, what do you make of these?
Error: unrecognized element in ISO Schematron namespace: check spelling
            and capitalizationparam
Schema implementation error: This schema has abstract patterns, yet they are supposed to be preprocessed out already
Cheers,
Martin
On 2021-02-01 10:38 a.m., Peter Stadler wrote:
...
...
Am 01.02.2021 um 19:33 schrieb Martin Holmes :
Are these irrelevant distractions? They aren't suppressed in the tei-log-parse-rules file in the Jenkins repo.
I don’t know. But I think in general it makes sense to fail the build when there are errors. Which I’ve just checked and so the build is marked as failed. I see that your Jenkins is happily going on with the build, so probably you haven’t checked this box?
If those errors are indeed non-brainers we should add it to the log-parse-rules
Peter
--
------------------------------------------
Martin Holmes
UVic Humanities Computing and Media Centre
-- 
------------------------------------------
Martin Holmes
UVic Humanities Computing and Media Centre