In Dockerfile, remove dependencies on old jenkins

[cmungall]

ontology-development-kit/Dockerfile

Line 37 in 0dd8ddb

RUN wget http://build.berkeleybop.org/userContent/owltools/owltools -O /tools/owltools && \

old Jenkins down. This was never a good idea anyway. There are multiple other sane things we can do instead:

• add the jar/owltools cli to owltools releases on GH
• release on mvncentral WIP: Removing dependency on local maven repo [knife] owlcollab/owltools#175
• build on a different jenkins
• build as part of docker build (no longer a prob now we are no longer alpine)
• any number of other things

note: since old jenkins down many old travisses will fail since they directly grabbed owltools and robot from there... but this is good, will force a switch to odk!

cc @kltm @matentzn

[kltm]

Okay, this is a hack, but we actually publish all the software that we use in the pipeline at the moment. E.g.: http://release.geneontology.org/2020-03-25/bin/ .
That can be used as an immediate drop-in to prevent failure until a better pick-up point is made.

[matentzn]

I would prefer add the jar/owltools cli to owltools releases on GH and will do that before the next ODK release..

[dougli1sqrd]

I made a new owltools release here: https://github.com/owlcollab/owltools/releases/tag/2020-04-06

[matentzn]

This release is missing a bunch of jar files I am used to from the old Jenkins:

ontology-development-kit/Dockerfile

Line 37 in 0cd1a1e

RUN wget http://build.berkeleybop.org/userContent/owltools/owltools -O /tools/owltools && \

Can we somehow add them as part of the release?

[matentzn]

http://build.berkeleybop.org/userContent/owltools/owltools http://build.berkeleybop.org/userContent/owltools/ontology-release-runner
http://build.berkeleybop.org/userContent/owltools/owltools-oort-all.jar

Were previously available.. :) sorry

[cmungall]

@dougli1sqrd can you add these? Thanks!

[balhoff]

Oops, sorry I already did this. Commented on two other tickets but missed this one.

[matentzn]

Done. #334