I’m following this with increasing concern! Syd and Martin and I scheduled to meet this afternoon (3pm in my EST timezone) to see if we can get a new Jenkins running in Pittsburgh on a supercomputer node that we have access to. The rule here is that anything in Docker has to be wrapped in a Singularity image, and there are some setup issues I don’t understand yet, but I wonder whether A) we want to concentrate on getting this new Jenkins up and running ASAP, or B) it’s better right now to concentrate on getting Victoria and Paderborn on their feet... Or both? Anyway, I wonder if our meeting today is turning into a rescue operation...should others join in? Elisa -- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text Associate Professor of English University of Pittsburgh at Greensburg 150 Finoli Drive, Greensburg, PA 15601 USA E-mail: ebb8@pitt.edu | Development site: http://newtfire.org Typeset by hand on my iPad

On Jan 20, 2018, at 10:26 AM, Syd Bauman wrote:

I committed a change to GitHub TEIC/TEI/ dev branch last night, 13 hours ago according to GitHub.

I do not understand the difference between the TEIP5-dev, TEIP5-Documentation-dev, and TEIP5-Test-dev jobs on Jenkins. But looking at http://jenkins.tei-c.org/view/TEI%20dev/, it is clear that none of these jobs has run for at least 18 hours. Shouldn't at least one of them?

Why won't Mr. Jenkins build the new dev branch of the TEI Guidelines?

I think he hates me. Snif. -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived