Closed fauust closed 2 years ago
In order to have labels working, I needed to use the next
docker container version of the server (not latest
).
I am willing to close this issue if someone can confirm that this is expected.
next
is the dev version built from master, not latest
.
next
is the dev version built from master, notlatest
.
Yes, that was pretty clear to me but it does not respond to my question..
latest is latest stable the lable feature is a breaking change and so is only in next until v1.0.0 got released
I am still not getting the real problem of this issue. You are using a self compiled version (similar to next tag) for the agent and the server, but the agent is not connecting or not picking up jobs?
Hmm, I will rephrase since you probably miss-understood my question.
Is it normal that an agent compiled from master needs a container server from next
in order for labels to work, if that's the case, then this issue can be closed?
Thanks.
Okay, now I get it. Partly yes. A server should use the same version as the agents, but as long as the protocol (GRPC) between the two wasn't change older versions will work as well. In the case of the reworked label feature which you tried to use we changed the GRPC definition and therefore you need a new server and agent.
I am still not getting the real problem of this issue. You are using a self compiled version (similar to next tag) for the agent and the server, but the agent is not connecting or not picking up jobs?
Nope everything works like a charm when I use same server/agent version:
woodpeckerci/woodpecker-server:next
)That was not the case with the following:
woodpeckerci/woodpecker-server:latest
)I could not find in the documentation something that would discourage to do such setup (and it may be needed if it's expected).
We planned on adding a warning #1114.
Warning: This is probably normal since the problem appears only with the dev version of the agent.
Component
server, agent
Describe the bug
As explained on matrix, labels are not working in my setup and I was suggested to open an issue here.
Here is my agent env:
Started with
go run ./cmd/agent --log-level debug
from the master branch (f21d8541).And here is my pipeline as suggested by https://woodpecker-ci.org/docs/administration/backends/local#using-labels-to-filter-tasks:
The exec agent refuse to execute the pipeline and the other docker agent (configured with docker-compose) is always selected. Here is the configuration of the docker-compose agent:
System Info
Additional context
No response
Validations