SPIKE: review how to cache conda env builds within or between workflows #9
Labels
cmascience
cmascience related rep
pipelines/workflows
Automated pipelines / workflows / actions via GitHub
question
Further information is requested
S.Slow (> 2 days)
sprint ready
Issue is ready to work on
Milestone
As a system developer I want the automated tests to run quickly and efficiently use the github actions allowance, so that tst results return quickly and incurred costs are kept low
Research options and methods to avoid the need to keep re building the conda env in each job, e.g. for test, edn2end tests, setup etc
The text was updated successfully, but these errors were encountered: