\n\nThis id number isn't helpful for viewing, as people don't have the IDs of all their CI runners memorized. It'd be much better to use the agent name (or alias / whatever you tagged it as) instead, and possibly default to the ID if no name is present.\n\n### Suggested solution\n\nUse the agent name / alias instead of an id number for the queue badge.\n\n### Alternative\n\n_No response_\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [x] Checked that the feature isn't part of the `next` version already [https://woodpecker-ci.org/versions]\n- [x] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [x] Check that there isn't already an [issue](https://github.com/woodpecker-ci/woodpecker/issues) that request the same feature to avoid creating a duplicate.",[3203],{"name":3180,"color":3181},5469,"In the queue list, use the agent name rather than the agent id for the badge.","2025-08-29T18:27:54Z","https://github.com/woodpecker-ci/woodpecker/issues/5469",0.77012444,{"description":3210,"labels":3211,"number":3215,"owner":3155,"repository":3156,"state":3216,"title":3217,"updated_at":3218,"url":3219,"score":3220},"In the agent's flags, there seems to be the ability to specify some filters:\r\nhttps://github.com/woodpecker-ci/woodpecker/blob/a07f120d1245bab2c6eb4f896cbc3348f5e04d72/cmd/drone-agent/flags.go#L67-L71\r\n\r\nIt says we can restrict builds by label — perfect, but it's not clear what those labels are or what the filters look like.\r\n\r\nI've been digging through the code a little bit, and it turns out that:\r\n\r\n1: this has examples of the filter syntax: https://github.com/woodpecker-ci/expr/blob/164b8b3d0915b31a990c04f93e20928ed67a45fb/selector_test.go#L11\r\n\r\n2: the below defines the 'filter function' — one thing I notice is that it seems to be that if you specify a filter, you MUST manually specify `platform == ...` in that filter otherwise you won't be filtering by platform anymore (The 'platform' is special-cased into the `filter.Labels` map at some point leading up to here, but I've lost track)\r\nhttps://github.com/woodpecker-ci/woodpecker/blob/a07f120d1245bab2c6eb4f896cbc3348f5e04d72/server/rpc.go#L494-L518\r\n\r\n3: this below is where the labels are attached to the Task\r\nhttps://github.com/woodpecker-ci/woodpecker/blob/master/server/hook.go#L390-L395\r\n\r\n4: it seems like this might be specifiable as a `labels` map in the pipeline YAML, but that part is not entirely clear to me — seems to be `libcompose.SliceorMap`.\r\n\r\n\r\nPoint (2) seems like a bug to me — surely you shouldn't be able to bypass the platform filter.\r\nBut in any case, none of this seems documented (please point it out if it is :)) and it'd be nice to change that (I'm happy to do so, just wanted to know if I'm missing anything / not understanding properly).",[3212],{"name":3213,"color":3214},"documentation","7D625D",304,"closed","`filters` / `Labels` are not very well documented.","2022-05-30T23:12:18Z","https://github.com/woodpecker-ci/woodpecker/issues/304",0.68739986,{"description":3222,"labels":3223,"number":3228,"owner":3155,"repository":3156,"state":3216,"title":3229,"updated_at":3230,"url":3231,"score":3232},"### Clear and concise description of the problem\n\nCurrently there is no way to limit where to limit agents where pipelines without any filter labels specified to run on.\n\n### Suggested solution\n\nAdd configuration option for woodpecker server to set default label filters that would be set for pipelines that has no filter set.\r\n\r\nThis could also be used as alternative to fix #2634\n\n### Alternative\n\nAs workaround this possible be also implemented in external configuration service but that seems not so straightforward and could be harder to implement\n\n### Additional context\n\nGitlab CI implements similar approach to allow for agents to set option that they are allowed to run \"untagged pipelines\"\n\n### Validations\n\n- [X] Checked that the feature isn't part of the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [X] Check that there isn't already an [issue](https://github.com/woodpecker-ci/woodpecker/issues) that request the same feature to avoid creating a duplicate.",[3224,3227],{"name":3225,"color":3226},"server","5D7A92",{"name":3149,"color":3150},4324,"Allow configuration option to specify default filter labels","2024-11-14T21:23:44Z","https://github.com/woodpecker-ci/woodpecker/issues/4324",0.6890908,{"description":3234,"labels":3235,"number":3238,"owner":3155,"repository":3156,"state":3216,"title":3239,"updated_at":3240,"url":3241,"score":3242},"### Clear and concise description of the problem\n\nThe endpoint to fetch pipelines queues currently returns all pipelines regardless of their labels.\r\nThis is problematic for #999 because I would like to be able to create different auto-scaled agent pools.\r\n\n\n### Suggested solution\n\nAdd filters in queues list endpoint by label set so I get a view of only the pipelines my agent pools can handle.\n\n### Alternative\n\nOptional / Nice-to-have: Add an option to label prometheus time series about queues with the same labels.\n\n### Additional context\n\n### Use cases\r\n\r\n#### Different autoscaler agent pool\r\n\r\n*Additional Information*: #999 \r\n\r\nA simple use-case is that I would like to have a pool of Instances (Virtual Machines) for `Docker` backend runners that use a pre-built docker image and just start the agent with the good parameters, the first start would be a *cold boot* because the volume would need to be initiated etc but the instance would be powered-off and re-spinned when needed with the same volume (*hot boot*).\r\n\r\nAnother pool for the `Local` backend runners would recreate (*cold boot*) a complete VM at each runs for cases where containers are not fitting and we want to run directly inside a VM.\r\n\r\nFinally, I would use Cloud Providers' managed Kubernetes for the `Kubernetes` backend and fine-tunes the settings for Woodpecker.\r\nIf I take @scaleway as an example, we have [Kapsule](https://www.scaleway.com/en/kubernetes-kapsule/) and it would be really easy to auto-scale the cluster horizontally by adding nodes as the number of container / the average per node CPU / memory starts to saturate.\r\n\r\nBut to make that work well I need to be able to get queues status per label `backend` so it auto-scales based on the right metrics (the queue length of the respective backends)\n\n### Validations\n\n- [X] Checked that the feature isn't part of the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]\n- [X] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/main/CONTRIBUTING.md).\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [X] Check that there isn't already an [issue](https://github.com/woodpecker-ci/woodpecker/issues) that request the same feature to avoid creating a duplicate.",[3236,3237],{"name":3225,"color":3226},{"name":3149,"color":3150},2803,"Per-labelset queues","2024-06-24T21:59:20Z","https://github.com/woodpecker-ci/woodpecker/issues/2803",0.7173712,{"description":3244,"labels":3245,"number":3248,"owner":3155,"repository":3156,"state":3216,"title":3249,"updated_at":3250,"url":3251,"score":3252},"auto add labels for `backend type` and `arch` and `os` (platform) to agent\r\n\r\n... and document them all nicenly :)\r\n\r\nto decide: should we only expose `arch&os` or only `platform` or both? ",[3246,3247],{"name":3177,"color":3178},{"name":3149,"color":3150},1178,"Autoset labels based on backend","2023-04-03T10:49:51Z","https://github.com/woodpecker-ci/woodpecker/issues/1178",0.7204965,{"description":3254,"labels":3255,"number":3256,"owner":3155,"repository":3156,"state":3216,"title":3257,"updated_at":3258,"url":3259,"score":3260},"### Clear and concise description of the problem\r\n\r\nAs a user of Woodpecker I want to use the agent hostname as a pipeline constraint so that I can force specific agents for a deployment pipeline.\r\n\r\n**Real Life Example**\r\n- 1 server\r\n- 2 local agents (same docker-compose file)\r\n- 2 support agents far far away :-)\r\n\r\nOne of the pipeline is a continuous deployment process which creates, signs and uploads artifacts. But the access to the corresponding fileserver is restricted to the local agents only.\r\n\r\n### Suggested solution\r\n\r\nWe already use the `WOODPECKER_HOSTNAME` environment variable to force agents hostname. Maybe we can match it again an additional `when` property.\r\n\r\n### Alternative\r\n\r\nWe can introduce a `node` constraint property in the pipeline syntax similar to Drone :-)\r\n\r\nUggly alternative I'm using here https://github.com/friendica/friendica/pull/11112 :\r\n- Set `WOODPECKER_PLATFORM` to a fictive value (like `releaser/release`)\r\n- add a `platform: releaser/release` constraint\r\n- örks ... :D\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Validations\r\n\r\n- [X] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/master/CONTRIBUTING.md).\r\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\r\n- [X] Check that there isn't already an [issue](https://github.com/woodpecker-ci/woodpecker/issues) that request the same feature to avoid creating a duplicate.",[],643,"Use the agent hostname as pipeline constraint","2022-09-15T20:33:53Z","https://github.com/woodpecker-ci/woodpecker/issues/643",0.7442924,["Reactive",3262],{},["Set"],["ShallowReactive",3265],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fgREoMMweBrOU6XLUp7dKCopuvUbElL7FWoXNV6o-STc":-1},"/woodpecker-ci/woodpecker/740"]