kernelci / kernelci/kernelci-deploy
Simplify new system deployment reusing `kci-easy`
- Dominant language
- Python
- Stars
- 4
- Forks
- 19
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 3
Description
Staging script currently deploys the new system by [running docker-compose actions](https://github.com/kernelci/kernelci-deploy/blob/main/staging.kernelci.org#L332).
It could be beneficial to align it with how `kci-easy` deployment works when it is adopted as a default development environment. It would help keeping staging instance as close as possible to the environment developers test on locally.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the docker-compose actions in staging.kernelci.org around line 332, then compare them with how kci-easy deployment works. Determine the deployment steps that should be shared so staging stays close to the default development environment. Done means the staging deployment reuses the kci-easy approach rather than its current separate actions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100