Enable azure releases and some fixes

[jneira]

• It makes release for all jobs (total 24), example: https://dev.azure.com/jneira/haskell-ide-engine/_build/results?buildId=371&view=artifacts&type=publishedArtifacts
• It fixes the z3 installation for macos
• It adds the hoogle databse generation, needed for tests
• It fixes the cache for windows, make it like the unix and macos ones
  • I've open an issue upstream: Error in post-job step of CacheV2 task: tar: Write error microsoft/azure-pipelines-tasks#12070
• I've make some advancesin the task that uses cabal to run the install.hs script but it still fails trying to install hie
• It adds specific triggers

The history is a liitle bit hairy, maybe it should be squashed.

[alanz]

I am thinking of starting a release process, should I wait for this first?

[fendor]

I dont think so, the artifacts dont work at the moment, iirc, since we havent solved the problem with hlint yet.
Moreover, azure is still not enaled for our repository, right?

[fendor]

LGTM.
As a minor suggestion, being more verbose might be a good idea, e.g. all tar commads could have the -v flag. That has the advantage that we see what files are compressed or extracted.

[jneira]

After testing we already can use the hlint data file under the same directory of hie executable i've change the scripts to include it:

• with stack unpack hlint --stack-yaml=../$(YAML_FILE)we'll get the appropiate hlint version

I've added -vto all tar commands as suggested by @fendor

[jneira]

I am thinking of starting a release process, should I wait for this first?

@alanz @fendor i think we could start the release process labeling it as beta after merging this:

• There is a unofficial azure account named haskell-ide-engine: https://dev.azure.com/haskell-ide-engine/ created by @power-fungus with builds from @power-fungus and @fendor repos
  • Maybe we could connect the default haskell-ide-engine project to @alanz one and use it as the main one until we get permissions to link the haskell org repo (or use fendor's one or mine)
• We could upload manually all the artifacts to github (until we get to automatically publish the artifacts to github) or/and point to azure releases
• Testing previously the precompiled binaries in clean environments
• Waiting for the issues opened by users that want to give a try to them

[alanz]

I just sent a mail to the haskell committee, who manage the haskell organisation on github, I think.

Hopefully they can do something for us.

[jneira]

I think it could be merged so if nobody disagree i'll do a squash&merge soon

[hvr]

Where do I need to go to enable Azure releases for this repo?

[jneira]

@hvr thanks a lot!

• I think you might do all from github settings > Integration Services > Azure Pipelines (it navigates to a wizard)
• In some step it asks how to configure the project an we should choose "Existing Azure Pipelines YAML file"
• Maybe you could consider invite to The Azure Pipelines Project any of github maintaners with the appropiate permissions: in https://dev.azure.com/${account}/${project} there is a link to do it

let me know if you want more details

[alanz]

@jneira Given this is a CI PR, which generally has a pretty boring and not useful history, I am ok with a squash merge, if that is what you want to do.