Hacks in the NEO build process prevent branches from coexisting
Closed this issue · 1 comments
Currently, the NEO build has an early stage that pushes neo.obo and neo.owl to S3 bucket go-build/build-noctua-entity-ontology/latest/; this is reflected in the real world as the PURLs http://purl.obolibrary.org/obo/go/noctua/neo.* and http://purl.obolibrary.org/obo/go/noctua-obo/neo.* (https://github.com/OBOFoundry/purl.obolibrary.org/blob/master/config/go.yml#L43-L47)
This means that anything branched off of the current NEO pipeline (issue-35-test) will publish these products, causing disruptions in anything that is picking up a neo.* product directly. (@balhoff ran into this.)
Looking at this, I believe it can be safely silenced in the branches, as it does not seem to (any longer?) be self-referential.
Brushed by on at geneontology/minerva#301 and geneontology/pipeline#35
This seems to be working now.