Add a github action workflow that builds and publishes the assets to a release, based on the release tag.
This makes it easier to setup a coti fullnode, since we don't need to build the projects locally anymore and can download the needed binaries straight from the release assets.
It also adds the advantage that a node no longer requires the installation of the java SDK (the JRE will be enough to run the java application).
The action will build the assets whenever a new tag in the format 0.0.0 is added (example: 3.2.0) and adds the assets to the release that matches that tag. So everytime a new release is added (and contains a tag in the 0.0.0 format), the action will trigger to build the assets and upload it to that release.
Here is an example of how the release looks like after the github action has ran:
Add a github action workflow that builds and publishes the assets to a release, based on the release tag.
This makes it easier to setup a coti fullnode, since we don't need to build the projects locally anymore and can download the needed binaries straight from the release assets.
It also adds the advantage that a node no longer requires the installation of the java SDK (the JRE will be enough to run the java application).
The action will build the assets whenever a new tag in the format 0.0.0 is added (example: 3.2.0) and adds the assets to the release that matches that tag. So everytime a new release is added (and contains a tag in the 0.0.0 format), the action will trigger to build the assets and upload it to that release.
Here is an example of how the release looks like after the github action has ran: