Skip to content
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 Stack/LTS for CI builds #1974

Closed
paf31 opened this issue Mar 26, 2016 · 3 comments
Closed

Use Stack/LTS for CI builds #1974

paf31 opened this issue Mar 26, 2016 · 3 comments
Milestone

Comments

@paf31
Copy link
Contributor

paf31 commented Mar 26, 2016

As long as we have reproducible builds and a simple way to get new contributors up and running, I don't see a need to build against multiple GHC versions any more, since Stack will download the correct version of GHC anyway.

Why not just standardize on a single LTS version (which can change over time)?

@hdgarrood
Copy link
Contributor

Also, on the topic of simplifying CI, are we using coveralls any more? I'm not sure what happened but their bot seems to have stopped commenting on PRs a while ago.

@paf31
Copy link
Contributor Author

paf31 commented Apr 20, 2016

I think it'd be nice to have Coveralls working again. It seems to run, just doesn't show notifications any more.

@paf31
Copy link
Contributor Author

paf31 commented Apr 21, 2016

Closing as dupe of #2034

@paf31 paf31 closed this as completed Apr 21, 2016
@paf31 paf31 added duplicate and removed question labels Apr 21, 2016
paf31 pushed a commit that referenced this issue May 8, 2016
* Switch to stack for CI, resolves #1974

* Remove the stack-nightly.yaml, since it always needs updating.
  Instead, we pass --resolver=nightly in one of the build jobs to ensure
  we always have the latest nightly. As an added bonus we no longer have
  to set the STACK_YAML environment variable on Windows, because
  stack.yaml is no longer a symlink.
* Remove use of cabal-install, which drastically simplifies the CI
  scripts :)
* Use the 'compiler' key in the build matrix as a hack to ensure each
  build job gets a separate cache.
* Add OSX tests.
* Add haddock tests, on a separate build job (for speed).
* Use separate build jobs for sdist tests (for speed).
* Fix binary bundle uploading on Travis
* Add binary bundle uploading for OSX.

* Update appveyor CI

* No longer need to set STACK_YAML on AppVeyor
* We should not attempt to run 'strip' on Windows executables
* Fix path to bundle creation script
@paf31 paf31 mentioned this issue May 22, 2016
19 tasks
archaeron pushed a commit to archaeron/purescript that referenced this issue Apr 6, 2017
* Switch to stack for CI, resolves purescript#1974

* Remove the stack-nightly.yaml, since it always needs updating.
  Instead, we pass --resolver=nightly in one of the build jobs to ensure
  we always have the latest nightly. As an added bonus we no longer have
  to set the STACK_YAML environment variable on Windows, because
  stack.yaml is no longer a symlink.
* Remove use of cabal-install, which drastically simplifies the CI
  scripts :)
* Use the 'compiler' key in the build matrix as a hack to ensure each
  build job gets a separate cache.
* Add OSX tests.
* Add haddock tests, on a separate build job (for speed).
* Use separate build jobs for sdist tests (for speed).
* Fix binary bundle uploading on Travis
* Add binary bundle uploading for OSX.

* Update appveyor CI

* No longer need to set STACK_YAML on AppVeyor
* We should not attempt to run 'strip' on Windows executables
* Fix path to bundle creation script
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants