a152d97e3c
Harbormaster can send a request in url encoded form while buildkite expects a POST request with json. Instead of modifying harbormastar or buildkite this adds a simple proxy that accepts url encoded form and creates a request that buildkite expects. To avoid potential abuse, nginx asks for simple http auth credentials stored in harbormaster. All build parameters passed by proxy are put into build metadata and as ph_* env variables available during the build. Secrets involved: - harbormastert knows http-auth to proxy (stored in privatly and in k8 buildkite/http-auth as auth file); - proxy knows buildkite api token (mine atm); - build agent knows conduit API token (mine atm), and SSH key of llvm-premerge-tests-bot (in k8 buildkite/github-ssh). Sample build: https://reviews.llvm.org/harbormaster/build/64828/8/ https://buildkite.com/llvm-project/premerge/builds/48 |
||
|---|---|---|
| .. | ||
| agent-debian-testing-buildkite | ||
| agent-debian-testing-ssd | ||
| agent-windows-buildkite | ||
| agent-windows-jenkins | ||
| agent-windows-vs2017 | ||
| agent-windows-vs2019 | ||
| base-debian | ||
| buildbot-mlir-nvidia | ||
| buildkite-premerge-debian | ||
| jenkins-master | ||
| nginx-results | ||
| build_deploy.ps1 | ||
| build_deploy.sh | ||
| build_run.ps1 | ||
| build_run.sh | ||
| README.md | ||
Overview
This folder contains files related to the machines running the build/test/checks for the merge guards.
Scripts
The scripts are written in bash (for Linux) and powershell (for Windows).
build_run.(sh|ps1)
Build the docker image and run it locally. This is useful for testing it.
build_deploy.(sh|ps1)
Build the docker and deploy it to the GCP registry. This is useful for deploying it in the Kubernetes cluster.