runboat
runboat copied to clipboard
sbidoul
A simple runbot lookalike on kubernetes. Main goal is replacing the OCA runbot.
updates: - [github.com/pre-commit/pre-commit-hooks: v4.5.0 → v4.6.0](https://github.com/pre-commit/pre-commit-hooks/compare/v4.5.0...v4.6.0) - https://github.com/charliermarsh/ruff-pre-commit → https://github.com/astral-sh/ruff-pre-commit - [github.com/astral-sh/ruff-pre-commit: v0.1.6 → v0.4.3](https://github.com/astral-sh/ruff-pre-commit/compare/v0.1.6...v0.4.3)
![pre-commit-ci[bot] avatar](https://avatars.githubusercontent.com/in/68672?v=4 "pre-commit-ci[bot] avatar"){kind=avatar}
It's there for a long time(days) without undeploying. How can I force delete? Now I can't deploy anything from the same branch.
When a build is created for a repo, and later the repo is removed from the configured supported repo, the cleanup of such builds fail with ``` Traceback (most recent...
Runboat screenshot: Details  Unpkg.com screenshot: Details 
https://runboat.odoo-community.org/api/v1/builds/b552cf370-23e2-4ce6-b081-f2a76e741cc9/init-log All runboat builds are failing on 14.0 branch in sale-workflow. @sbidoul @lmignon
Apparently, when `notify_status()` fails, normal operations are stuck.
Some features depends of the use of HTTPS, for example service workers. 
When some builds are initialized but fail to start and CrashLoopBackOff, runboat does not correctly account for the number of started builds and let the cluster run out of pods....
When a pod fails on startup, the `logs` link is never displayed in the UI, so the reason of the failure is not surfaced to user. Related to #59