GHC artifact collector
This is the application that collects GHC build artifacts created on Circle CI and AppVeyor.
ghc-artifact-collector - collect GHC build artifacts Usage: ghc-artifact-collector [-t|--as-tool TOOL-NAME] FILE GHC artifactor collector Available options: -h,--help Show this help text -t,--as-tool TOOL-NAME Upload file as a tool with this name. FILE File to store.
If S3 variables are not set, do nothing (important because we don't want PRs from forks to fail because of this, and those PRs won't have S3 variables set). S3 environment variables:
The variables mean what their names suggest.
If branch is not
masterand the build has been triggered not by a tag push, do nothing. Note that one has to add filtering by tags in order to enable building on tag pushing on CircleCI. (This is unless
--as-toolis used. With that option branch and tag do not matter, but it's used only to deploy the
If there is no tag, use the following object keys:
metadata.jsonfile contains some metadata describing how the bindist was obtained (SHA1 of commit, etc.).
In addition to that, the first artifact in the list of files to upload will be copied to this (more) stable location:
If there is a tag, use the following prefix:
Similarly, the latest version of artifact will be copied to this location:
nightly/folder is expected to be configured with such life cycle policy that old files are automatically deleted, e.g. after a month.
Copyright © 2018 Tweag I/O
Distributed under BSD 3 clause license.