summaryrefslogtreecommitdiff
path: root/.gitlab-ci.yml
Commit message (Collapse)AuthorAgeFilesLines
* gitlab-ci: Only build x86_64-deb8 and fedora27 for releasesBen Gamari2019-02-231-2/+6
| | | | These are largely redundant as they are covered by x86_64-deb9.
* Use validate flavour rather than devel2 for DEBUG CI jobMatthew Pickering2019-02-221-1/+1
| | | | This also builds stage2 with optimisations and -dcore-lint
* Set builder envTamar Christina2019-02-211-0/+2
|
* CI: Run `cabal update` before trying to build HadrianMatthew Pickering2019-02-201-0/+1
|
* Fix and Reapply "Performance tests: recover a baseline from ancestor commits ↵David Eichmann2019-02-161-1/+30
| | | | and CI results."
* Add explicit dependencies to cleanup-darwinMatthew Pickering2019-02-121-0/+1
|
* Make CI via Hadrian build docsAlec Theriault2019-02-101-0/+1
|
* Revert "gitlab-ci: More aggressive artifact expiration"Matthew Pickering2019-02-071-10/+17
| | | | This reverts commit d87b38a2519212aaf8bad927c65abecc509a7212.
* gitlab-ci: More aggressive artifact expirationBen Gamari2019-02-071-17/+10
|
* gitlab-ci: Add a devel2 buildBen Gamari2019-02-071-0/+10
|
* gitlab-ci: Don't allow x86_64-linux-deb9-llvm to failBen Gamari2019-02-041-1/+0
|
* Turn on -Werror when validatingMatthew Pickering2019-02-021-1/+1
|
* Revert "Performance tests: recover a baseline from ancestor commits and CI ↵Ben Gamari2019-01-311-29/+1
| | | | | | | | | results." Unfortunately this has broken all future commits due to spurious(?) performance changes which I have been unable to work around. This reverts commit cc2261d42f6a954d88e355aaad41f001f65c95da.
* gitlab-ci: Use build cleanup logic on Darwin as wellBen Gamari2019-01-301-3/+21
| | | | | We use the shell executor on Darwin as well as Windows. See https://gitlab.com/gitlab-org/gitlab-runner/issues/3856.
* Performance tests: recover a baseline from ancestor commits and CI results.David Eichmann2019-01-301-1/+29
| | | | gitlab-ci: push performance metrics as git notes to the "GHC Performance Notes" repository.
* Revert "Batch merge"Ben Gamari2019-01-301-50/+4
| | | | This reverts commit 76c8fd674435a652c75a96c85abbf26f1f221876.
* Batch mergeBen Gamari2019-01-301-4/+50
|
* gitlab-ci: Fix Windows cleanup command lineBen Gamari2019-01-271-1/+4
| | | | | Why is it so hard to delete a directory's contents without deleting the directory itself in Windows? This will forever remain a mystery.
* gitlab-ci: Explicitly clear dependencies of all jobsBen Gamari2019-01-231-0/+4
| | | | | | | Apparently GitLab CI defaults to declaring all jobs of the previous stage as dependencies of a job. This meant that we would end up downloading all of our binary distributions during the `cleanup` stage, eating up a truly remarkable amount of S3 tranfers.
* gitlab-ci: Drop CircleCI jobsBen Gamari2019-01-231-30/+0
| | | | | | It's pretty unlikely we will be going back to circleci at this point [skip-ci]
* gitlab: Collect artifacts on WindowsBen Gamari2019-01-231-0/+10
|
* Update Darwin CI to use new toplevel --with-intree-gmp configure flagAlec Theriault2019-01-231-1/+1
|
* gitlab-ci: Disallow failureBen Gamari2019-01-231-1/+0
|
* gitlab-ci: Reenable Hadrian build on WindowsBen Gamari2019-01-231-6/+5
|
* gitlab-ci: Cleanup Windows buildsBen Gamari2019-01-141-0/+30
| | | | See Note [Cleanup on Windows].
* gitlab-ci: Clone haddock from its upstream repositoryBen Gamari2019-01-071-1/+1
| | | | This ensures that changes requiring haddock changes can be built under CI.
* gitlab-ci: Try reenabling PDF documentation on DarwinBen Gamari2019-01-061-2/+0
| | | | Carter says that the builder issues have now been sorted.
* configure: introduce HAPPY and ALEX vars and deprecate --with-ghc in favour ↵Adam Sandberg Eriksson2019-01-011-2/+2
| | | | | | of the GHC var Also updates the windows gitlab ci to use the new configure variables.
* gitlab-ci: Try only building Windows in the quick flavourBen Gamari2018-12-251-0/+1
| | | | | | It seems no matter how many machines I throw at Windows it's constantly behind. Perhaps the quick build flavour will be fast enough to allow us to keep until while we sort out our toolchain issues (#16084).
* gitlab-ci: Allow Windows to fail for nowBen Gamari2018-12-251-2/+4
| | | | While we sort out #16084.
* gitlab-ci: Require that integer-simple configuration passesBen Gamari2018-12-251-2/+1
| | | | The last step of #15915.
* gitlab-ci: Clean tree on Windows after jobBen Gamari2018-12-241-0/+1
| | | | | It seems like currently the runner doesn't delete the working tree after finishing a job. At least we can delete the binary artifacts for now.
* gitlab-ci: Use robocopy instead of bash to copy cabal cacheBen Gamari2018-12-241-1/+1
|
* gitlab-ci: Use per-build temporary directory on WindowsBen Gamari2018-12-241-3/+12
| | | | | | | I have seen several instances of inexplicable "Access denied" errors on Windows. Using per-build temporary directories avoids any chance of interference between builds and eliminates the possibility of temporary files leaking beyond the life of the build.
* gitlab-ci: Disable CircleCI Darwin buildsBen Gamari2018-12-231-1/+1
| | | | They aren't finishing correctly anyways.
* gitlab-ci: Allow Darwin CircleCI build to failBen Gamari2018-12-221-0/+1
| | | | | This is currently spuriously failing. Moreover, we have the Mac Mini builder running again so this is much less necessary now.
* gitlab-ci: Fix Darwin buildBen Gamari2018-12-211-1/+4
| | | | Previously the toolchain directory was wiped away by git clean.
* gitlab-ci: Only run nightly-i386-linux-deb9 when NIGHTLY is setBen Gamari2018-12-211-0/+3
|
* gitlab-ci: More aggressive cleaningBen Gamari2018-12-211-2/+3
|
* gitlab-ci: Only run CircleCI Darwin build in full-build stageBen Gamari2018-12-211-0/+1
|
* gitlab-ci: Add i386 Debian 9 buildsD5440Ben Gamari2018-12-211-0/+24
|
* gitlab-ci: Ensure that build environment is cleanBen Gamari2018-12-211-1/+3
|
* gitlab-ci: Set localeBen Gamari2018-12-211-0/+2
|
* gitlab-ci: Set thread count properly on WindowsBen Gamari2018-12-211-2/+2
|
* gitlab-ci: Tag linter stageBen Gamari2018-12-211-0/+14
| | | | | | | Previously the linters were tagged with x86_64-linux, meaning that linting jobs would often get stuck behind builds in the queue. Given that linting jobs are fairly low-cost they hold up later build stages it is important that we reduce this latency.
* gitlab-ci: Fix Windows buildBen Gamari2018-12-211-18/+20
|
* gitlab-ci: Remove CircleCI configurationBen Gamari2018-12-211-12/+0
| | | | Our CircleCI builds will fail anyways without large instances.
* gitlab-ci: Allow Hadrian build on Windows to failBen Gamari2018-12-211-0/+2
| | | | Due to #16073.
* Revert "gitlab: Drop submodules hack"Ben Gamari2018-12-211-2/+20
| | | | | | | It turns out that the submodules hack is useful to ensure that CI works in forks. This reverts commit 90ceafa8b9ad60e3c7b72cdd2dacdbeb96bdcddc.
* gitlab-ci: Split build into two halvesBen Gamari2018-12-191-4/+15
| | | | | | | | | | | Currently we are having quite some trouble keeping up with our build volume due to the number of configurations we have. I've split the pipeline into two halves: * build, which builds just vanilla deb9-linux with make and hadrian * full-build, which builds everything else This will trade-off some latency to more efficient use of our builders.
View Lorry Controller Status