Lauris BH

In docker if agents are scaled in docker and multiple agent instances are run in same docker host... they would have same persistent volume attached that could be a problem...

> well I would not implement autoscaling by spowning new threads ... and instead refactor the loop in the agent implementation to only have one main loop and use go...

Maybe woodpecker server could provide temporary docker registry for docker build images? This would also allow testing built images in separate pipeline and starting them as services. There could be...

Yes but would be nice if that could be specified somehow also in pipeline (with having setting for default value if not specified)

Yes but if you have private gitea instance and public repo (still accessible only by authorization) you will have public woodpecker repository that will be accessible without authorization that is...

New search looks a bit too unreadable (background/foreground contrast)

I don't think this issue is fixed... For me after upgrading from 1.16.x to 1.17.1 had still issues with lot of owner teams

I know, I had to fix this for 70 organizations 😁 manually updated in database with sql

Ideally this should be fixed by migration but we are too late for that in 1.17 release, probably migration for 1.18 + doctor command to fix this

I will reopen this as this still can be a problem to many