From 4057446c64e447b5ca4e8cbabfe5eb9ccebbccc9 Mon Sep 17 00:00:00 2001 From: Jens Petersen Date: Fri, 19 Jan 2024 11:15:38 +0800 Subject: [PATCH] CURATORS: a couple more lts workflow updates [skip ci] --- CURATORS.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/CURATORS.md b/CURATORS.md index e17f4b04..1fb854ea 100644 --- a/CURATORS.md +++ b/CURATORS.md @@ -227,7 +227,7 @@ Supported versions: ... update-global-hints.hs: Received ExitFailure 1 when running ``` -Also required to build an LTS minor bump with a ghc version change: On the build server, modify `/var/stackage/stackage/automated/work/lts-$THIS_LTS_MAJOR_VER/constraints.yaml` and update the ghc-version. (You may need to update sibling files as well.) Then run `NOPLAN=1 /var/stackage/stackage/automated/build.sh lts-$THIS_LTS_MINOR_BUMP` to build the LTS. +Also required to build an LTS minor bump with a ghc version change: modify and update the ghc-version. Then run `automated/build.sh lts-$THIS_LTS_MINOR_BUMP` to build the LTS. ### Getting the new image to the build server Once a new Docker image is available, you'll need to pull it onto the stackage-build server (see @@ -336,8 +336,6 @@ to avoid having to rebuild everything again.) Note LTS builds without NOPLAN will use the last Hackage data. You may need to `run-nightly.sh` to get a newer package, but this should be less common for lts. -~~If you need to make further modifications beyond what `constraints.yaml` allows, you can directly edit the `snapshot-incomplete.yaml` file. Then, instead of `NOPLAN=1 build.sh`, you need to use `NOPLAN=2 build.sh`. Note that from this point on, further changes to `constraints.yaml` will not impact the build plan.~~ - ### Timing A looping script on the build server keeps trying to build nightly