Use doit and GitHub actions
bollwyvl opened this issue · comments
What are you trying to do?
Improve time to implement new features and test fixes.
How is it done today, and what are the limits of current practice?
We currently use:
anaconda-project- brittle environment locking (if used)
- non-intuitive how to replace some parts
- mental model required of what to do next
- challenges with cross-platform dependencies
- Azure Pipelines
- extra complexity vs. in-house on GitHub
What is new in your approach and why do you think it will be successful?
Using approaches from wxyz, gt-coar-lab and robotframework-jupyterlibrary, we should be able to achieve equivalent/better development and testing, fairly rapidly.
Who cares? If you are successful, what difference will it make?
Developers, and users of new features.
What are the risks?
N/A
How much will it cost?
Wear and tear on Ctrl, V and C.
How long will it take?
Couple hours.
What are the mid-term and final “exams” to check for success?
- Working locally
- Working binder
- Working on GitHub Actions