squakez opened a new issue, #6858:
URL: https://github.com/apache/camel-k/issues/6858
Right now we have too many repeated
```
{"level":"info","ts":"2026-09-28T16:33:18Z","logger":"camel-k.controller.build","msg":"Maximum
number of running builds (1) exceeded - the build (kit-dat9dasflfds73d4ejhg)
gets
enqueued","request-namespace":"test-738cfc29-92d9-404e-a02d-9b0984d7b6a2","request-name":"java-bhhmii","max-running-builds-limit":1,"api-version":"camel.apache.org/v1","kind":"Build","ns":"test-738cfc29-92d9-404e-a02d-9b0984d7b6a2","name":"kit-dat9dasflfds73d4ejhg"}
```
Beside reducing the number of messages about the parallel execution, we
should find a better way to reduce the logic.
We should change the existing
```
type scheduleAction struct {
baseAction
lock sync.Mutex
reader ctrl.Reader
buildMonitor Monitor
}
```
to remove the synchronous code and just leverage instead the `MAX_PIPELINES`
env var introduced recently where the configuration is stored.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
