eca78eb366
maybe we will later use same agents for everything but for now I don't want to modify working build much. But I have updated deployment of release agent to use correct docker image (there were renamed a while ago) and pass tags and agent token via env variables. Have not deployed new deployment for release yet. |
||
|---|---|---|
| .. | ||
| agent-debian-testing-buildkite | ||
| agent-debian-testing-ssd | ||
| agent-windows-buildkite | ||
| agent-windows-jenkins | ||
| agent-windows-vs2017 | ||
| agent-windows-vs2019 | ||
| buildbot-mlir-nvidia | ||
| 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.