Release 5.2.0
Due by January 10, 2025
10% complete
Develop Outside, Run Inside
This milestone will introduce a workflow enabling researchers to develop this research and analysis code outside of the TRE, using whatever tools they prefer and are familiar with, and bring this work into the TRE to run against the sensitive data.
This would improve for researchers,
- Reproducibility (as users would be encourag…
Develop Outside, Run Inside
This milestone will introduce a workflow enabling researchers to develop this research and analysis code outside of the TRE, using whatever tools they prefer and are familiar with, and bring this work into the TRE to run against the sensitive data.
This would improve for researchers,
- Reproducibility (as users would be encouraged and enabled to use public VCS repositories)
- User experience
- User efficiency
- Accuracy of results (as testing code is easier)
For managers there will be,
- Lower support burden for managing ingress of code
- Greater automation
In detail,
- Painless system for data ingress (focused on code) with automation
- Targeting using internal Gitea instance to create read-only mirrors of external repositories
- System (possibly automated) for researchers to request repository mirrors
- Additional guidance/automation for other data ingress e.g. container images