afed3a7898
I have tried to install new windows machine for buildkite and updated some scrips and docs on along the way. - Updated base image for k8s agent installation as it gave a warning that previous version was old. - Now buildkite secret is configured in a powershell script along with tags (and possible other parameters). - Split "windows_agent_start.ps1" to "..jenkins" and "..buildkite" as some parameters are different. - Created a "windows-development" machine in GCP stat can be resumed to build docker images / expriment. |
||
|---|---|---|
| .. | ||
| 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.