Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[STORY] Specify Arcana version installed in deployments #73

Closed
tclose opened this issue May 12, 2022 · 2 comments
Closed

[STORY] Specify Arcana version installed in deployments #73

tclose opened this issue May 12, 2022 · 2 comments
Labels
deploy-framework Deployment framework epic mid-level Requires moderate framework/domain-specific knowledge pipelines story a unit of work
Milestone
Release

Comments

@tclose
Copy link
Contributor

tclose commented May 12, 2022 •
edited
Loading

Description

When building and deploying pipelines, we should be able to specify the Arcana version that is installed inside the deployment docker images (i.e. for the XNAT container service). Currently the same version as is used to build the docker images is installed inside the the images, but we may want to freeze the Arcana version inside the images in some circumstances for reproducibility considerations.

Acceptance Criteria

  • Arcana version installed inside Docker images should be able to be specified in build/deployment workflow
@tclose tclose added this to the 2.0.0b milestone May 12, 2022
@tclose
Copy link
Contributor Author

tclose commented Jun 19, 2022

Epic: Australian-Imaging-Service/pipelines#33

@tclose tclose moved this to Backlog in AIS Master Project Jun 20, 2022
@tclose tclose changed the title Specify Arcana version installed in deployments [STORY] Specify Arcana version installed in deployments Jun 20, 2022
@tclose tclose added story a unit of work and removed enhancement labels Jun 20, 2022
This was referenced Jun 20, 2022
Open
Open
@tclose tclose added deploy-framework Deployment framework epic mid-level Requires moderate framework/domain-specific knowledge ready labels Jun 21, 2022
@tclose
Copy link
Contributor Author

tclose commented Aug 8, 2022

Thinking about this some more I reckon that this unnecessarily complicates things. We can always freeze the Arcana version by selecting a specific version to build the images with. And since we will aim for Arcana to be backwards compatible and not affecting the actual results, there theoretically shouldn't be any reason not to use the latest version.

@tclose tclose closed this as completed Aug 8, 2022
@tclose tclose moved this to Done in AIS Master Project Aug 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
deploy-framework Deployment framework epic mid-level Requires moderate framework/domain-specific knowledge pipelines story a unit of work
Projects
None yet
Milestone
Release
Development

No branches or pull requests
1 participant
@tclose