Re: [Tei-council] Travis ne Jenkins ne local

There seems to be a bug in Jenkins whereby if I define a global log-parsing file, log-parsing fails, but if I specify the same file on a per-project basis, with an explicit system path, it works. It's one of many things that show up as different/broken when moving forward from my old Jenkins (Ubuntu 14.04 to Ubuntu 18.04). Cheers, Martin On 2018-10-05 01:45 AM, Peter Stadler wrote:

Just another note on the ci services: Travis (for the Guidelines repo) is only running the tests, i.e. a `make clean validate test`. Jenkins is running three jobs, a) the tests (same as travis), b) TEIP5-Documentation (which I think we could drop), and c) the complete build

Only the last one is failing, hence the difference between travis and Jenkins.

Peter

PS: Yes, log parsing seems to be broken on Martin’s Jenkins, at present

...

Am 05.10.2018 um 05:57 schrieb Syd Bauman :

The dev branch now has all the deprecations valid until 2018-10-01 removed, and its build working ala Travis. However, said build is not working in Jenkins (on either jenkins or jenkins2 -- for some reason the former does not have parsed console output, but it is the same error), and is working on my local system, after a fashion.