Create branch to generate Reactome pathway GO-CAMs

[dustine32]

Hoping this isn't a duplicate ticket.

Create a branch with a simplified Jenkinsfile to complete the following tasks:

• [ ] Pull current release human BioPAX file from Reactome
• [ ] Pull current go-lego.owl file from GO
• [ ] git pull origin master of geneontology/pathways2GO repo
• [ ] mvn package and run bin/pathways2go.jar to generate TTL files
• [ ] Push these TTL files to skyhook

Next step would be to commit these TTL files to the geneontology/reactome-go-cams and geneontology/noctua-models repos. We can start handling this step manually for now.

Frequency of this pipeline running could be manual for now. Maybe set up a recurring schedule or (more complex) somehow detect a new Reactome release and then trigger this pipeline.

@kltm You may have an opinion about whether we use the code in git versus pulling a release jar (like we do in the ontology build to generate reacto.owl)

[kltm]

A few questions/comments here:

• wouldn't this best fit in the general pipeline branches; why make it separate?
  • why would these go to skyhook, rather than the repo in GH? the latter is more stable
• it looks like something similar that we had in an earlier version of the neo pipeline that ben had; it might be worth digging into the history there and remembering some do's and don't's