As a follow up on #1 I propose we create an archive of the file-pattern-scanner and upload it on the release we have now automated.
The archive should be zip or tar.gz or both. It should contain the groovy files needed to run, and some docs (maybe readme).
To upload binaries on releases in Github we first need to get an upload url: https://developer.github.com/v3/repos/releases/#get-a-single-release
Then upload the binary with that url: https://developer.github.com/v3/repos/releases/#upload-a-release-asset
As a follow up on #1 I propose we create an archive of the file-pattern-scanner and upload it on the release we have now automated.
The archive should be zip or tar.gz or both. It should contain the groovy files needed to run, and some docs (maybe readme).
To upload binaries on releases in Github we first need to get an upload url: https://developer.github.com/v3/repos/releases/#get-a-single-release
Then upload the binary with that url: https://developer.github.com/v3/repos/releases/#upload-a-release-asset