As the repository lives in github, it should be implented as github actions.
https://github.com/toolforge/buildpack-admission-controller
The CI should:
- Run pre-commit on the whole code
- Run go tests (see readme)
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Stalled | LucasWerkmeister | T320140 Migrate wd-shex-infer from Toolforge GridEngine to Toolforge Kubernetes | |||
| Stalled | matmarex | T319707 Migrate dtcheck from Toolforge GridEngine to Toolforge Kubernetes | |||
| Open | None | T320062 Migrate steve-adder from Toolforge GridEngine to Toolforge Kubernetes | |||
| Open | None | T320011 Migrate rfa-voting-history from Toolforge GridEngine to Toolforge Kubernetes | |||
| Open | dcaro | T194332 [Epic] Make Toolforge a proper platform as a service with push-to-deploy and build packs | |||
| In Progress | dcaro | T267374 [tbs.beta] Create a toolforge build service beta release | |||
| Open | None | T325187 tbs: user-story 13: I want to avoid getting bugs inadvertently into the codebases | |||
| In Progress | None | T325192 tbs: user-story 13: Add ci to the buildpack-admission-controller repo |
Event Timeline
Comment Actions
As the repository lives in github, it should be implented as github actions.
What is blocking us from migrating this repo to GitLab? See T327057
Comment Actions
We can go ahead with this on github for now, adding a simple command (pre-commit), we'll move to gitlab at a later stage