-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EPIC] Deployment framework for community and custom XNAT container service pipelines #33
Open
3 of 17 tasks
Labels
Comments
tclose
changed the title
Container service pipelines deployment framework
Deployment framework for community and custom XNAT container service pipelines
Jun 18, 2022
This was referenced Jun 18, 2022
Open
Open
tclose
changed the title
Deployment framework for community and custom XNAT container service pipelines
[EPIC] Deployment framework for community and custom XNAT container service pipelines
Jun 20, 2022
tclose
added
incomplete-desc
deploy-framework
Deployment framework epic
and removed
incomplete-desc
labels
Jun 20, 2022
This was referenced Sep 19, 2022
1 task
This was referenced Sep 29, 2022
This was referenced Oct 1, 2022
2 tasks
This was referenced Jul 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hypothesis Statement
Description
For AIS users who design their own workflows or use community-developed pipelines the Container service pipelines deployment framework is a framework for deploying custom and community-generated pipelines to the AIS. Unlike handcrafting Docker images compatible with XNAT's container service, in our solution XNAT-CS-compatible Docker images are fully specified by recipes with minimal boiler plate (particularly in comparison to the XNAT command.JSON). The Docker images are automatically built and deployed to the AIS. Workflow provenance is also stored alongside the generated derivatives for future reference.
Outcomes
Leading Indicators
Nonfunctional Requirements
Features
Tasks
The text was updated successfully, but these errors were encountered: