awslabs / awslabs/eks-perf-tests
[testing] Pipelines and tasks configuration changes
- Dominant language
- Shell
- Stars
- 72
- Forks
- 50
- PR merge metrics
- No merged PRs in 30d
Description
- Today we have pipelines and runs in the same directory, we should separate them out
- Add meaningful names to these so user don't have to go look inside the YAML spec to figure out what tasks/pipelines are doing
- We need a way to properly to name things -
- Tasks should be like `eks-cluster-create-using-awscli` or `eks-cluster-delete-using-awscli`, `kit-cluster-control-plane-create` or `kit-cluster-control-plane-delete`
- All these tasks should run in their own namespace something like `kit-testing` and use default service-account
Contributor guide
Research direction
Locate the directory containing the pipelines, runs, tasks, and YAML specifications, then inventory how they are currently organized and named. Done means pipelines and runs are separated, tasks have meaningful names, and all tasks use the agreed namespace and default service account.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100