Remove builds from all ontologies' metadata

Makefile

@@ -51,7 +51,7 @@ integration-test: test valid-purl-report.txt
 
 # Remove and/or revert all targets to their repository versions:
 clean:
-	rm -Rf registry/ontologies.nt registry/ontologies.ttl registry/ontologies.yml sparql-consistency-report.txt jenkins-output.txt valid-purl-report.txt valid-purl-report.txt.tmp _site/ tmp/ reports/
+	rm -Rf registry/ontologies.nt registry/ontologies.ttl registry/ontologies.yml sparql-consistency-report.txt valid-purl-report.txt valid-purl-report.txt.tmp _site/ tmp/ reports/
 	git checkout _config.yml registry/ontologies.jsonld registry/ontologies.ttl registry/ontologies.yml
 
 
@@ -236,10 +236,5 @@ valid-purl-report.txt: registry/ontologies.yml
 sparql-consistency-report.txt: registry/ontologies.yml
 	./util/processor.py -i $< sparql-compare > $@.tmp && mv $@.tmp $@
 
-# output of central OBO build
-# See FAQ for more details, and also README.md
-jenkins-output.txt:
-	wget http://build.berkeleybop.org/job/simple-build-obo-all/lastBuild/consoleFull -O $@
-
 reports/%.csv: registry/ontologies.ttl sparql/%.sparql
 	arq --data $< --query sparql/$*.sparql --results csv > $@.tmp && mv $@.tmp $@

README.md

@@ -116,36 +116,6 @@ do is make further edits to fix the syntax error.
 
 TODO: add a quick guide to yaml, and the tags we use.
 
-## Central OBO library build
-
-(see also the FAQ entry on this)
-
-The central OBO build runs here:
-
- * http://build.berkeleybop.org/job/simple-build-obo-all/
-
-It takes as metadata input the yml file from this repository. It makes
-use of the `build` object.
-
-The output of this job is a set of obo and owl files deposited in
-
- * http://berkeleybop.org/ontologies/
-
-Depending on the build configuration, this may also make additional files. See for example:
-
- * http://berkeleybop.org/ontologies/uberon/
-
-A http://berkeleybop.org/ontologies/ URL should never be handed out directly. This service exists so that:
-
- * Un PURL-registered ontologies will have a fall-through
- * Registered PURL ontologies that do not want to take charge of either OBO or OWL generation will have a place to 302-redirect to
-
-This job will fail if ontologies marked as `infallible` fail. To debug, the full log of the last build can be examined:
-
- * https://build.berkeleybop.org/job/simple-build-obo-all/lastBuild/consoleFull
-
-(Look for the text "should not fail")
-
 ## Instructions for Website Development
 
 See [README-sitedev.md](README-sitedev.md)