-
-
Notifications
You must be signed in to change notification settings - Fork 367
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use cabal-install if nix is failing in CI #1859
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I hope this would unblock #1858 🙂
@jneira Branch protection rules need updates correspondingly We should remove:
And add:
|
you could do it no yourself right now 🙂 (but i did the change anyways to merge asap) |
# Build and then push HLS binaries with developmet shell to cachix | ||
# This job runs when PRs are merged to master, and should be excluded from branch protections | ||
build: | ||
runs-on: ${{ matrix.os }} | ||
if: ${{ github.repository_owner == 'haskell' && github.ref == 'ref/heads/master' }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It didn't run as expected :(
https://github.com/haskell/haskell-language-server/actions/runs/870310690
We have decided to maintain the nix packaging (building HLS binaries in nix) in #1827. Ideally, we are always have HLS binaries prepared without
cabal-install
. However, PRs that update project dependencies like #1858 may be blocked by nix ci, since nixpkgs does not have the new dependency yet, and even if it has, a bump of nixpkgs is required. It's unreasonable to require every contributor to handle nix things, so this PR add a fallback in CI, which usescabal-install
to build HLS in case some required packages are missing in nixpkgs.Also adds
default.nix
, so that the legacynix-build
can work.