This week I published a
drone/drone:0.5.0 image that includes the new embedded message broker. This release candidate introduces stable agent <> server communication protocol. Although the protocol is stable, you should expect the release candidate to be unstable given the magnitude of this change. So in other words, help me find the bugs!
Below is a summary of some notable changes.
The primary different with agent setup is that you need to provide the full URL to the broker endpoint using the appropriate websocket scheme. This is an example:
Or if your server is using SSL:
Also please ensure you are using the secret instead of the token for authorizing agent to server communication. The token has been deprecated.
If you are using a reverse proxy (nginx, caddy, apache) with drone the configuration should be much more simple. We have removed the long-polling in favor of websockets. All websockets share the same
/ws base path.
The only real change to the yaml is that plugins must include
plugins/ in the image name. We are no longer pre-pending it. So you may need to update your images accordingly
Agent CLI Commands
drone agents command for listing connected agents it not yet working with the new queue. You will need to monitor agent and server logs to verify connectivity until this is re-implemented.