REF: use xnat4test for CI #164
Open
Conversation
This file contains 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.
Replace xnat-docker-compose setting used in CI for testing administrative and user related pyxnat features for a simpler approach using a single Docker container deployment of XNAT via xnat4tests.
New XNAT deployment is installed as a Python dependency package and can be operated via CLI in the CI workflow script. XNAT instance is now operable by default at localhost:8080 (instead of localhost:80).
An additional/unrelated change has been included (REF: use randomly created projects for sessionmirror tests), to avoid collisions between CI workflow runs when testing
sessionmirrorscript against the very same XNAT (central) entities. Now uses randomly generated projects created (and removed) on the fly at execution time.PR closes #163.