- Mar 05, 2024
-
-
There were a few issues with the hackage links: 1. We were using the package id rather than the package name for the package links. This is fixed by now allowing the template to mention %pkg% or %pkgid% and substituing both appropiatly. 2. The `--haddock-base-url` flag is renamed to `--haddock-for-hackage` as the new base link works on a local or remote hackage server. 3. The "src" path including too much stuff, so cross-package source links were broken as the template was getting double expanded. Fixes #24086
-
This adds the upload of ghc-internal and ghc-experimental to our scripts which upload packages to hackage.
-
- Mar 01, 2024
-
-
Here we enable documentation building on 1. Darwin: The sphinx toolchain was already installed so we enable html and manpages. 2. Rocky8: Full documentation (toolchain already installed) 3. Alpine: Full documetnation (toolchain already installed) 4. Windows: HTML and manpages (toolchain already installed) Fixes #24465
-
9.6.4 is currently broken due to #24050 Also update to use LLVM-15 rather than LLVM-11, which is out of date.
-
We have previously bumped the docker images to use 9.6.4, but neglected to bump the windows images until now.
-
- Feb 26, 2024
-
-
- Feb 21, 2024
-
-
- Feb 17, 2024
-
-
This commit bumps our ci-images revision to use updated wasm image.
-
- Feb 08, 2024
-
-
This is mainly experimental and future proofing to enable a smooth transition to newer alpine releases once 3_12 is too old.
-
- Jan 10, 2024
-
-
- Jan 04, 2024
-
-
- Nov 21, 2023
-
-
[skip ci]
-
- Nov 01, 2023
-
-
This brings it into line with the x86 LLVM backend job.
-
As the Debian 10 images have too old an LLVM. Addresses #24056.
-
- Oct 10, 2023
-
-
This adds a rule which triggers the javascript job when the "javascript" label is assigned to an MR.
-
-
- Oct 07, 2023
-
-
- Oct 05, 2023
-
-
- Sep 26, 2023
-
-
Due to #23979.
-
- Sep 21, 2023
-
-
So that it is visible by default.
-
libiserv has been merged into the ghci package.
-
- Sep 19, 2023
-
-
This adds a debian 11 release job for aarch64. Fixes #22005
-
This is dynamically linked and makes creating statically linked executables more straightforward. Fixes #23482
-
- Sep 12, 2023
-
-
This bumps the minumum supported version to 10.13 (High Sierra) which is 6 years old at this point. Fixes #22938
-
- Sep 08, 2023
-
-
This adds builds for the latest releases for fedora and debian We build these bindists in nightly and release pipelines.
-
- Aug 30, 2023
-
-
- Aug 25, 2023
-
-
- Aug 23, 2023
-
-
We now build the relocatable bindist target on windows, which means we test and distribute the new method of creating a relocatable bindist.
-
- Aug 21, 2023
-
-
The test-primops CI job requires some additional builds in the validation pipeline, so we make sure to enable these jobs when test-primops label is set.
-
- Aug 16, 2023
-
-
This will cause any CI job to fail if we have a mismatch between what ghc-toolchain reports and what ./configure natively reports. Fixing these kinds of issues is highest priority for 9.10 release.
-
Fixes #23737
-
- Aug 14, 2023
-
-
-
-
In particular we now distinguish between whether we are dealing with a Nightly/Release pipeline (which labels don't matter for) and a validate pipeline where labels do matter. The overall goal here is to allow a disjunction of labels for validate pipelines, for example, > Run a job if we have the full-ci label or test-primops label Therefore the "ValidateOnly" rules are treated as a set of disjunctions rather than conjunctions like before. What this means in particular is that if we want to ONLY run a job if a label is set, for example, "FreeBSD" label then we have to override the whole label set. Fixes #23772
-
* We now represent a job group a triple of Maybes, which makes it easier to work out when jobs are enabled/disabled on certain pipelines. ``` data JobGroup a = StandardTriple { v :: Maybe (NamedJob a) , n :: Maybe (NamedJob a) , r :: Maybe (NamedJob a) } ``` * `jobs-metadata.json` generation is reworked using the following algorithm. - For each pipeline type, find all the platforms we are doing builds for. - Select one build per platform - Zip together the results This way we can choose different pipelines for validate/nightly/release which makes the metadata also useful for validate pipelines. This feature is used by the test-primops downstream CI in order to select the right bindist for testing validate pipelines. This makes it easier to inspect which jobs are going to be enabled on a particular pipeline. -
This was causing some confusion as the job was named simply "x86_64-linux-deb10-validate", which implies a standard configuration rather than any dependency on libzstd.
-
- Aug 04, 2023
-
-
This test passes on dynamically-linked Alpine. (cherry picked from commit f356a7e8)
-
