Stop and clean CDDS workflows
- Dominant language
- Python
- Stars
- 5
- Forks
- 3
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 8
Description
Following #354, if a CDDS workflow does not succeed, it must be stopped and cleaned before attempting to re-run CMEW.
**Acceptance criteria**
- **Given** a working CMEW workflow
- **When** a CDDS workflow fails
- **And** the `standardise_model_data` job fails
- **Then** the `housekeeping` job stops and cleans all CDDS workflows
Note: The `housekeeping` task currently runs at the end of the workflow, but could be run after `restructure_dirs` (since it only cleans up CDDS-related data), and will need to be run for each `dataset`.
Contributor guide
Research direction
Trace the CDDS workflow and its existing housekeeping task, paying attention to the standardise_model_data and restructure_dirs steps. Verify how housekeeping is scheduled and how datasets are iterated; done means a failed standardise_model_data run stops and cleans all CDDS workflows before CMEW can be rerun.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100