Repository navigation
T023: the release's 15 species, the Jenkinsfile's command, the xml:base check - #86
Merged
Merged
Conversation
…se check -s now takes a list of species ids, each written to its own file, and a species named there with no events ends the run with exit 1. The Jenkinsfile passes the 15 species of release 98's published zip; whether to add Mycobacterium tuberculosis is issue #84. The stray quote that ended its docker run line is gone, and the credentials reach the shell as variables. CI's fixture job runs the release's own xml:base check (the DownloadDirectory step's grep), which passes for the fixture's release and fails for another, and its second run uses the list form. The command's shape was run from an image built from this branch against the private fixture graph, zipped as the Jenkinsfile does, and checked as the release checks. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
adamjohnwright
added a commit
that referenced
this pull request
Oct 29, 2026
From #86's review: the Jenkinsfile's credentials quoted, what a bad id writes
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replaces #85, with its review's findings fixed.
Spec 001, T023.
-snow takes a list of species ids, each written to its own file (one id still works). The Jenkinsfile passes the 15 species of release 98's publishedbiopax.zip, read from those files' ownxml:base. Whether to add Mycobacterium tuberculosis, which has events of its own but has never been published, is Should the release's BioPAX files include Mycobacterium tuberculosis? #84. If yes, it is one more id in the Jenkinsfile.docker runline, which would have stopped the shell, is gone. The jar is the image's entry point, and-o ./outputlands in the mounted folder..owlinbiopax.zipmust holdxml:base="http://www.reactome.org/biopax/{release}. CI's fixture job now runs the same check. It passes for the fixture's release (98) and fails for another (97).--network=host, the mount,-o ./output,-swith the two species the fixture graph holds) against the private fixture graph;zip -r, and the release's check on the unzipped files: two files, both with the release's base.The release server's own run is the release's, and its timing is T024.
-s 48887,170928. A bad species id exits 1. 93 tests pass, and actionlint is clean.-sthat has no events now ends the run with exit 1. The release's check counts files, so it wouldn't notice one missing. Shown with a species added to the private fixture graph for the run and removed after.$user/$passinstead of being filled in by Groovy./after the release number, so release 9 would match 98's files. The list of 15 is kept in step by hand.🤖 Generated with Claude Code