The sever requires the DRONE_HOST environment variable and will exit when not properly configured. This setting is used to generate commit status links and lets encrypt certificates, and in the future will be used to more accurately perform oauth2 redirects.

Please note that grpc uses http/2 and cannot be routed through a reverse proxy (i.e. nginx). If you are using nginx you must bypass and connect the agent directly with the server.

Repository Syncing

Previous versions of drone synchronized repository and permission data in-memory and used sql hacks to provide the intersection of the in-memory and sql datasets. This approach had known performance limitations.

This release synchronizes the repository list to the database. This is now possible thanks to universal support of the INSERT IGNORE and INSERT REPLACE statements. The sql hacks are replaced with standard joins.

This new approach could result in repository permissions taking longer to propagate to drone. The user interface will also need to be improved to correctly handle data post-synchronization.

What’s Next

Future releases will continue to focus on reaching the 1.0 milestone and compatibility promise. There are currently less than 15 issues remaining before we can tag our first 1.0 release candidate. We expect subsequent minor releases following 1.0 (1.1, 1.2, etc) will focus on stabilizing and cleaning up the codebase, and removing technical debt.