aboutsummaryrefslogtreecommitdiffstats
path: root/builds.sr.ht
diff options
context:
space:
mode:
authorAnton Gusev <uartman@mail.ru>2021-02-14 19:19:32 +0300
committerDrew DeVault <sir@cmpwn.com>2021-02-15 08:34:47 -0500
commit8f1908614d6df6cacabe8e18559dc83f5727050f (patch)
tree9104de7e354bb846096890585804ab0535adee35 /builds.sr.ht
parentfd4b6f40b1f9c76f4b8ff24c826ab32ed4d62249 (diff)
downloadsr.ht-docs-8f1908614d6df6cacabe8e18559dc83f5727050f.tar.gz
Document BUILD_SUBMITTER and BUILD_REASON environment variables in build.sr.ht documentation
Environment variables BUILD_SUBMITTER and BUILD_REASON that show information about integrations are implemented, but not documented. This patch adds them to the list of environment variables and adds their values to the respective integration pages. Made in response to https://lists.sr.ht/~sircmpwn/sr.ht-discuss/<20210213233602.4dd7ae3113379f443fc0468e@mail.ru>
Diffstat (limited to 'builds.sr.ht')
-rw-r--r--builds.sr.ht/index.md24
1 files changed, 24 insertions, 0 deletions
diff --git a/builds.sr.ht/index.md b/builds.sr.ht/index.md
index c30dc2b..cf676f5 100644
--- a/builds.sr.ht/index.md
+++ b/builds.sr.ht/index.md
@@ -111,6 +111,13 @@ The following environment variables are defined for all builds:
- **JOB_URL**: The URL at which the build logs and information can be viewed
with a web browser
+The following environment variables are commonly added by
+[integrations](#integrations):
+
+- **BUILD_SUBMITTER**: The name of the integration which submitted the job
+- **BUILD_REASON**: The reason the integration submitted the build
+
+
# Build status badges
If you add tags to your build, or enter search terms, you can use these to
@@ -143,8 +150,25 @@ sources array, we'll edit it to point to the ref you just pushed. You can also
submit up to 4 builds on each push by providing `.builds/*.yml` (if more are
submitted, 4 manifests will be randomly chosen).
+**Environment**
+
+- `BUILD_SUBMITTER`: `git.sr.ht`
+
## hg.sr.ht
hg.sr.ht will also automatically submit builds for you. The naming conventions
and other details are the same as the process used by git.sr.ht - described
above.
+
+**Environment**
+
+- `BUILD_SUBMITTER`: `hg.sr.ht`
+
+## hub.sr.ht
+
+hub.sr.ht will automatically submit builds when a patch to a repo with `.build.yml` is sent to a mailing list.
+
+**Environment**
+
+- `BUILD_SUBMITTER`: `hub.sr.ht`
+- `BUILD_REASON`: `patchset`