Use HydraBuildList to provide latest release binaries (with fallback)

[tweakch]

Updating documentation

Issue

Fixes #299

Description of the change

I updated the links adding the latest-finished route to always use the latest pre-built binary (as stated in the NOTE)

These links resolve to the following build ids

• Linux: https://hydra.iohk.io/build/7630428
• MacOS: https://hydra.iohk.io/build/7630460
• Windows: https://hydra.iohk.io/build/7630442

Not sure if we should use them instead and lock the versions advertised in the admonition to v1.29...

I'll update the links accordingly if you guys think the build ids are a better solution.

[tweakch]

I just saw #267 which is indirectly related. I'll keep an eye out and open new issues when I find these mary / alonzo related things.

[rdlrt]

Unfortunately using latest-finished is not recommended as any PR/commit on node repo will create a new hydra build - which means it will not necessarily be compatible with mainnet/or include untested changes.

If we have to automate using release builds , the specific build number can be extracted from notes in release page (example below) :

curl -s https://api.github.com/repos/input-output-hk/cardano-node/releases/latest | jq .body | sed -e 's/.*Hydra binaries](\(.*\)#tabs-constituents.*/\1#tabs-constituents/'

In terms of documenting, I suppose we can either link them to cardano-node releases page to read release notes and use links from the description OR add a custom JS (equivalent to above) to dynamically build URL on client browser OR provide them bash instructions for command as above to fetch the correct build URLs?

[tweakch]

...not necessarily be compatible with mainnet/or include untested changes.

Of course... i always forget the mainnet policy.

curl -s https://api.github.com/repos/input-output-hk/cardano-node/releases/latest | jq .body | sed -e 's/.*Hydra binaries](\(.*\)#tabs-constituents.*/\1#tabs-constituents/'

Nice.

I think I'll add a dynamic link js. I think i can get it to work thanks to your stream editor expression

[tweakch]

what do you think about that?

HydraBuildList renders the links to the configured binaries and displays a link to the latest release if the latest prop does not match the latest relase build id from github...

CORS header AllowOrigin * is not configured on hydra preventing me from making a second request and extract the latest buildId on the client... That's something the server needs to do but that is too much IMO...

It's my first React component so please suggest improvements... i'll be happy to add them

[tweakch]

The current release build is 7408469 with build ids 7408438, 7408630 and 7408538 for linux, macos and win64 respectively.

Setting these Ids on HydraBuildList

:::note
<!-- omitted for brevity -->

<HydraBuildList
    latest="7408469"
    linux="7408438"
    macos="7408630"
    win64="7408538"/>

<!-- omitted for brevity -->
:::

Results in the following output:

If there is a new release of the binaries the latest buildId will change: (f.e. to 7500000)

HydraBuildList will now render the following ouput:

Giving us the chance to lookup the build ids of the cardano-node (f.e. 7500001,7500002,7500003) and update the component so the message about the new release will disappear again.

:::note
<!-- omitted for brevity -->

<HydraBuildList
    latest="7500000"
    linux="7500001"
    macos="7500002"
    win64="7500003"/>

<!-- omitted for brevity -->
:::

[katomm]

Awesome solution for this. (in the past we tried to put all versions into variables.js but we never manged to connect all the variables)

[gufmar]

Lgtm