Hi Hugh,
I think it is probably better just to make it common knowledge by reminding us lots that in writing good commit messages (not the crappy ones I tend to use) that avoiding the word 'error' and the word 'warning' are probably good ideas.
Many thanks,
James
--
Dr James Cummings, James.Cummings@newcastle.ac.uk
Senior Lecturer in Late-Medieval Literature and Digital Humanities
School of English, Newcastle University
________________________________
From: Tei-council on behalf of Hugh Cayless
Sent: 20 November 2018 12:50:40
To: TEI Council
Subject: Re: [Tei-council] Jenkins dislikes my commit message?
FYI I'm pretty sure it is possible to tell Jenkins to ignore specific messages, so there's a workaround available if you have a case where you really WANT to say "error" :-).
H
On Tue, Nov 20, 2018 at 7:02 AM James Cummings mailto:James.Cummings@newcastle.ac.uk> wrote:
Hi Syd,
I had that problem the other week with some otherwise benign changes where I mentioned "Error in listObject Example" (26 October) https://github.com/TEIC/TEI/commits you'll see immediately after I committed "inconsequential commit to trick Jenkins".
This is because the way Jenkins flags whether there is an error or not is parsing the console output for the word 'error'. Imagine how fun this would be if one of our tests returned "No errors here!". Sigh. So having it do it again won't do anything but find the same error it thinks exists because your commit message is present.
I'd suggest, if you haven't already, just making a trivial change, even just spacing, and re-committing/pushing without mentioning the word 'error'. ;-)
Best wishes,
James
--
Dr James Cummings, James.Cummings@newcastle.ac.ukmailto:James.Cummings@newcastle.ac.uk
Senior Lecturer in Late-Medieval Literature and Digital Humanities
School of English, Newcastle University
________________________________
From: Tei-council mailto:tei-council-bounces@lists.tei-c.org> on behalf of Syd Bauman mailto:s.bauman@northeastern.edu>
Sent: 19 November 2018 22:20:38
To: TEI Council
Subject: [Tei-council] Jenkins dislikes my commit message?
Could the Jenkins maintainers force the Stylesheets-dev job to
re-build?
My check-in from this morning's meeting built as well as can be
expected on my local system. It fails in Jenkins, flagging my commit
message itself (which contains the word "error"). I'm hoping that if
Mr. Jenkins just does the work again, it will work. If not, I'll try
committing some tiny tweak with a different commit message.
_______________________________________________
Tei-council mailing list
Tei-council@lists.tei-c.orgmailto:Tei-council@lists.tei-c.org
http://lists.lists.tei-c.org/mailman/listinfo/tei-council
_______________________________________________
Tei-council mailing list
Tei-council@lists.tei-c.orgmailto:Tei-council@lists.tei-c.org
http://lists.lists.tei-c.org/mailman/listinfo/tei-council
