Build haddock in CI

[michaelpj]

• Misc improvements around specification of compilers
• Build haddock derivations for components that have them

This should ensure nothing gets published with broken haddock. Let's see if we get away with it...

[michaelpj]

Ah indeed, we do know that haddock for things that depend on the plutus-tx plugin doesn't work. Not sure what the best way to exclude that is 🤔

[michaelpj]

Okay, this works but it's not very beautiful, wdyt @andreabedini ?

[andreabedini]

It looks ok to me. I allowed myself to make a little change to get the haddock published by Hydra. Maybe, I might need to pass them to the aggregate; also I never understood why Hydra is not showing the constituents.

[andreabedini]

Finally I figured out!

15:39:28 hydra-evaluator.1    | aggregate job ‘jobs.test’ has a constituent ‘/nix/store/04w2zdarr340slal8m9c25ccglvciqx5-cardano-node-lib-cardano-node-8.2.1-haddock.drv’ that doesn't correspond to a Hydra build
15:39:28 hydra-evaluator.1    | aggregate job ‘jobs.test’ has a constituent ‘/nix/store/33yg9xhz0qb4028k2306dyz7bs50smq7-cardano-node-lib-cardano-node-8.2.1.drv’ that doesn't correspond to a Hydra build
15:39:28 hydra-evaluator.1    | aggregate job ‘jobs.test’ has a constituent ‘/nix/store/j36fqba1ypli6sncfsma2910rlrvra1z-cardano-node-exe-cardano-node-8.2.1.drv’ that doesn't correspond to a Hydra build

The jobs you aggregate still have to be in the set of hydra jobs!

[michaelpj]

Looks fine, although it seems like we had a weird merge at some point.