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.

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

SPIKE: review how to cache conda env builds within or between workflows #9

Open
jonathan-winn-geo opened this issue Jul 29, 2020 · 2 comments
Assignees
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

Comments

@jonathan-winn-geo
Copy link
Collaborator

jonathan-winn-geo commented Jul 29, 2020

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

@jonathan-winn-geo jonathan-winn-geo added this to the Backlog milestone Jul 29, 2020
@jonathan-winn-geo jonathan-winn-geo self-assigned this Jul 29, 2020
@jonathan-winn-geo jonathan-winn-geo added 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 labels Oct 20, 2020
@github-project-automation github-project-automation bot moved this to To Do (long-term or to review) in cma-open-training Dec 23, 2024
@jonathan-winn-geo
Copy link
Collaborator Author

this will now be delivered under the workflows repo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
Status: To Do (long-term or to review)
Development

No branches or pull requests

1 participant