openzipkin
Make CI use script based convention used in other projects
If you don't mind, please move some of the logic inlined into ci.yml into build-bin, with a README and RELEASE.md like the other projects. Also, if you can, please change the GH actions file and job names so that they are basically the same (makes badges easier also).
Here's a couple examples:
- https://github.com/openzipkin/zipkin-ruby/pull/180
- https://github.com/openzipkin/zipkin-api
Motivation
We are standardizing build script and job names for easy reference when people switch from one project to another. It is important that the tasks done in CI do not heavily rely on CI specific tools as in the future we may get into trouble like this again. For example, in the past we had to switch from travis to circle back to travis. Using scripts we control as entrypoints gives us flexibility as CI providers change their policies around open source communities.
