Open dustine32 opened 3 weeks ago
Speaking with @kltm yesterday, I will PR the PANTHER_VERSION
change into Jenkinsfile
on all 6 of these relevant branches:
master
- PR: https://github.com/geneontology/pipeline/pull/400snapshot
- PR: #401snapshot-post-fail
- PR: #402release
- PR: #403derivatives-from-goa
- PR: #404go-raw-data
- PR: #405After merging these PRs into their branches I will scan repository on build to flush the changes so they don't run automatically.
Merged all six Jenkinsfile
PRs and scanned repository and aborted all launched runs. I then deleted the PR branches so they no longer would show on the Jenkins build UI.
With the go-site/metadata/go-reference-species.yaml
PR merged and pantherftp symlink switched, everything should be in place for the next snapshot
run.
@dustine32 @pgaudet Noting that we should now have PANTHER 19 propagated through snapshot
.
The official ticket for switching pipeline components to PANTHER 19.0 (from 17.0). Tested in https://github.com/geneontology/go-site/issues/2364.
PANTHER_VERSION
inJenkinsfile
. https://github.com/geneontology/pipeline/pull/400metadata/go-reference-species.yaml
ingo-site
to reflect new 19.0 species. https://github.com/geneontology/go-site/pull/2372