Forgejo 11 image for testing purposes #219
Conversation
… repository configuration with a pending action, and a runner registered Signed-off-by: jaime merino <jaime.merino_mora@mail.schwarz>
I wonder how this would work if you do not add the repository git files into this image? |
Hi, my approach is to just test the autoscaler that calls a Forgejo instance with a pending job state. With this image and a request to the right endopoint you get a new job waiting to be executed. But theres is no need to actual test the pipeline or the runner execution, it can be a hello world busybox image. |
|
Ah then this makes sense. I only looked at the github_runner e2e test that does run real jobs. |
|
here is the PR with the test example kedacore/keda#6495 |
|
Ah thanks, the last time I saw your PR this part was incomplete and you just updated it. If I would want to run your e2e tests on my machine, I have a small problem
AFAIK Recreating them out of the database is not possible, only the last eight tokens and a hash is in the database. Given the sqlite database is public, make them public? Document them somewhere? Only provide keda maintainers the values (no I am not part of keda)? Some bots in some keda repos seem to hunt potential secret leaks. E.g. my jwt token in the gitea config was marked yesterday. |
|
My idea is to share the tokens with the contributors of KEDA so they can add it to the github secrets. |
This PR adds a new Forgejo 11 image that includes a SQLite3 snapshot and an initialization setup file. It contains a minimal repository setup with a defined pipeline and a pending job, as well as a registered runner using a token that will be set externally.
Checklist
Fixes #