bcgov / bcgov/wps

Pipeline cleanup scripts suck

Open
#1,404 0 comments 0 reactions 0 assignees View on GitHub
4Refinement Task
Dominant language
Python
Stars
65
Forks
11
Avg merge
21h 25m
Merged PRs (30d)
70

Description

**Describe the task**
Our cleanup scripts intermittently fail to cleanup all resources. This results in resources slowly bleeding away until someone goes and does manual cleanups. It also results in errors in various parts of openshift as things get partially deleted.

**Acceptance Criteria**
- [ ] Cleanup always cleans up! Or lets us know when it fails.
- [ ] All relevant build configs are cleaned up. (e.g. wps-ubuntu-pr is not currently being cleaned)

**Additional context**
- Expecting PR imagestream etc. to be deleted. (Only imagestream left should be the one that's copied into the production imagestream)
- List build configs: oc -n e1e498-tools get BuildConfig --no-headers

Contributor guide

Open the contributing guide

Research direction

Start by listing the build configurations with `oc -n e1e498-tools get BuildConfig --no-headers` and trace the pipeline cleanup scripts that remove those resources. Done means cleanup reliably removes all relevant build configs and PR resources, leaves only the production imagestream copy, and reports failures instead of silently leaving partial deletions.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
ci-cd, devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.