haskell/stackage
1
0
Fork 0
mirror of https://github.com/commercialhaskell/stackage.git synced 2026-01-25 21:51:57 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

CURATORS: Update for new github docker images

Browse Source
This commit is contained in:
Adam Bergmark 2022-01-06 18:03:07 +01:00
parent 367fb9c88c
commit fd360cb4df
1 changed files with 4 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
CURATORS.md
View File

@ -206,12 +206,11 @@ If a new package fails to build because of missing system libraries we often ask
### Upgrading GHC version ### Upgrading GHC version
The Dockerfile contains information on which GHC versions should be used. You The Dockerfile contains information on which GHC versions should be used. You
can modify it and push it to Github to trigger a DockerHub build. The nightly can modify it and push it to Github to trigger a build. The nightly
branch is used for nightlies. For LTSes, we use the ltsX branch, where X is the branch is used for nightlies. For LTSes, we use the ltsX branch, where X is the
major version number (e.g., lts3 for lts-3.\*). major version number (e.g., lts3 for lts-3.\*).
Note that when starting a new LTS major release, you'll need to modify Docker Note that when starting a new LTS major release, you'll need to modify `.github/workflows/image.yml` to add a new lts branch.
Hub to create a new Docker tag for the relevant branch name.
Update `GHCVER` in `Dockerfile`. (This env var automatically gets passed to `debian-bootstrap.sh`.) Update `GHCVER` in `Dockerfile`. (This env var automatically gets passed to `debian-bootstrap.sh`.)
@ -241,7 +240,7 @@ docker rm $(docker ps -a -q)
docker rmi $(docker images -q) docker rmi $(docker images -q)
``` ```
but `docker pull commercialhaskell/stackage:nightly` can also be run instead just to update the nightly image say. but `docker pull ghcr.io/commercialhaskell/stackage/build:nightly` can also be run instead just to update the nightly image say.
For a new GHC version you should also delete the ~~cache~~ .stack-work snapshot install directories on the stackage-build server to For a new GHC version you should also delete the ~~cache~~ .stack-work snapshot install directories on the stackage-build server to
~~force all packages to be rebuilt~~ clear up some space. See: [issue#746](https://github.com/commercialhaskell/stackage/issues/746). Eg: ~~force all packages to be rebuilt~~ clear up some space. See: [issue#746](https://github.com/commercialhaskell/stackage/issues/746). Eg:
@ -555,8 +554,7 @@ Every 3-6 months, we make a new major release of LTS. The procedure we follow fo
relaxed upper bounds. There will likely be some hard decisions to be made relaxed upper bounds. There will likely be some hard decisions to be made
regarding relaxing a bound versus keeping more packages. All of these changes regarding relaxing a bound versus keeping more packages. All of these changes
occur on master and affect nightly. occur on master and affect nightly.
4. Once the estimated date hits, push a new `ltsXX` branch and trigger Docker 4. Once the estimated date hits, push a new `ltsXX` and wait for the docker image build.
Hub to build a Docker image for the new release.
5. Run the build procedure for the new LTS release. 5. Run the build procedure for the new LTS release.
6. After the LTS build completes, more aggressively prune upper bounds from 6. After the LTS build completes, more aggressively prune upper bounds from
`build-constraints.yaml`. `build-constraints.yaml`.