rel_eng: Add release engineering scripts into ghc tree
It is better to keep these scripts in the tree as they depend on the CI configuration and so on. By keeping them in tree we can keep them up-to-date as the CI config changes and also makes it easier to backport changes to the release script between release branches in future. The final motivation is that it makes generating GHCUp metadata possible.
Showing
- .gitlab-ci.yml 1 addition, 1 deletion.gitlab-ci.yml
- .gitlab/rel_eng/default.nix 54 additions, 0 deletions.gitlab/rel_eng/default.nix
- .gitlab/rel_eng/fetch-gitlab-artifacts/.gitignore 3 additions, 0 deletions.gitlab/rel_eng/fetch-gitlab-artifacts/.gitignore
- .gitlab/rel_eng/fetch-gitlab-artifacts/README.mkd 23 additions, 0 deletions.gitlab/rel_eng/fetch-gitlab-artifacts/README.mkd
- .gitlab/rel_eng/fetch-gitlab-artifacts/default.nix 13 additions, 0 deletions.gitlab/rel_eng/fetch-gitlab-artifacts/default.nix
- .gitlab/rel_eng/fetch-gitlab-artifacts/fetch_gitlab.py 145 additions, 0 deletions.gitlab/rel_eng/fetch-gitlab-artifacts/fetch_gitlab.py
- .gitlab/rel_eng/fetch-gitlab-artifacts/setup.py 14 additions, 0 deletions.gitlab/rel_eng/fetch-gitlab-artifacts/setup.py
- .gitlab/rel_eng/nix/sources.json 68 additions, 0 deletions.gitlab/rel_eng/nix/sources.json
- .gitlab/rel_eng/nix/sources.nix 194 additions, 0 deletions.gitlab/rel_eng/nix/sources.nix
- .gitlab/rel_eng/upload.sh 250 additions, 0 deletions.gitlab/rel_eng/upload.sh
- .gitlab/rel_eng/upload_ghc_libs.py 0 additions, 0 deletions.gitlab/rel_eng/upload_ghc_libs.py
Loading
Please register or sign in to comment