Jorge Turrado Ferrero

hey! Thanks! 🚀 I think that the correct endpoint is the pipeline one -> https://docs.gitlab.com/ee/api/pipelines.html But yeah, the idea is that KEDA will poll the queue length calling the API...

I've taken a look and it looks nice. It's exactly how a scaler works :)

@fira42073 , what do you need for the e2e tests? I'm a total newbie with Gitlab so IDK if we have to create a Gitlab account or if it runs...

Hello Sorry for the slow response :( > - how to actually perform all of these setup actions for the cases when gitlab-runner is tested in the e2e tests. I...

> If some other scaler already does such setup, could you please refer me to where I can see that? Sure! [This example creates the selenium hub from scratch using...

> I'll do my best to carve out some time for it this weekend. Thanks! No rush at all. We really appreciate contributions, but OSS is OSS. Take your time...

Interesting... as Gitlab already has an scaling system, should we have our own? @kedacore/keda-contributors I'm wondering if Gitlab exposes an API that we can use to get the current Jobs...

> > Interesting... as Gitlab already has an scaling system, should we have our own? @kedacore/keda-contributors > > I'm wondering if Gitlab exposes an API that we can use to...

To add the e2e tests, you can use ScaledJobs with just a dummy Gitlab runner that process a dummy job -> https://docs.gitlab.com/runner/install/docker.html My question would be if we can spin...

/run-e2e beanstalkd **Update:** You can check the progress [here](https://github.com/kedacore/keda/actions/runs/10482091832)