revi-archive/llvm-premerge-checks
1
0
Fork 0
Code Activity

Formatting and typos

Browse source
This commit is contained in:
Mikhail Goncharov 2019-10-10 09:27:31 +02:00
parent ce9e33f696
commit 5667321337
1 changed files with 18 additions and 16 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
README.md
View file

@ -8,12 +8,13 @@ TODO(@christiankuehnel): describe objective of merge guards
# Cluster overview # Cluster overview
The cluster consists of these services: The cluster consists of these services:
* Jenkins build server: [http://jenkins.llvm-merge-guard.org] * Jenkins build server: http://jenkins.llvm-merge-guard.org
* a set of Jenkins agents running the builds * a set of Jenkins agents running the builds
* an nginx server with the build results/logs [http://jenkins.llvm-merge-guard.org] * an nginx server with the build results/logs http://jenkins.llvm-merge-guard.org
# Jenkins-Phabricator integration # Jenkins-Phabricator integration
The Jenkins-Phabricator is based on the instructions provided with the [Phabricator-Jenkins Plugin](https://github.com/uber/phabricator-jenkins-plugin). The Jenkins-Phabricator is based on the instructions provided with the [Phabricator-Jenkins Plugin](https://github.com/uber/phabricator-jenkins-plugin).
On the Phabricator side these things were configured: On the Phabricator side these things were configured:
@ -29,13 +30,14 @@ There is no backup of the credentials. If you need to change it, generate a new
# Playbooks # Playbooks
## deployment to a clean infrastructure ## deployment to a clean infrastructure
General remarks: General remarks:
* GCP does not route any traffic to your services unless the service is "helthy". It might take a few minutes after startup before the services is classified as healthy. Until then you will only see some generic error message. * GCP does not route any traffic to your services unless the service is "healthy". It might take a few minutes after startup before the services is classified as healthy. Until then you will only see some generic error message.
These are the steps to set up the build server on a clean infrastructure: These are the steps to set up the build server on a clean infrastructure:
1. Configure the tools on your local machine: 1. Configure the tools on your local machine:
```bash ```bash
./setup.sh ./local_setup.sh
``` ```
1. Delete the old cluster, if it still exists: 1. Delete the old cluster, if it still exists:
```bash ```bash
@ -52,14 +54,14 @@ These are the steps to set up the build server on a clean infrastructure:
cd kubernetes/cluster cd kubernetes/cluster
./disk_create.sh ./disk_create.sh
``` ```
1. ssh into the VM instance mounting the volume, find the mount point and then set 1. SSH into the VM instance mounting the volume, find the mount point and then set
```bash ```bash
# go to the mount point of the volume # go to the mount point of the volume
cd /var/lib/kubelet/plugins/kubernetes.io/gce-pd/mounts/jenkins-home cd /var/lib/kubelet/plugins/kubernetes.io/gce-pd/mounts/jenkins-home
# change the permissions # change the permissions
sudo chmod a+rwx sudo chmod a+rwx
``` ```
1. push the docker images to gcr.io: 1. Push the docker images to gcr.io:
```bash ```bash
cd containers/debian-testing-clang8 cd containers/debian-testing-clang8
./build_deploy.sh ./build_deploy.sh
@ -67,12 +69,12 @@ These are the steps to set up the build server on a clean infrastructure:
cd ../jenkins-master cd ../jenkins-master
./build_deploy.sh ./build_deploy.sh
``` ```
1. Deploy the stack: `` 1. Deploy the stack:
```bash ```bash
cd kubernetes cd kubernetes
./deploy.sh ./deploy.sh
``` ```
1. configure it 1. Configure it
## handling SSH keys ## handling SSH keys
The Jenkins server SSHs into the agents to start the agent application. Thus the master needs SSH access to the agent. To set this up: The Jenkins server SSHs into the agents to start the agent application. Thus the master needs SSH access to the agent. To set this up: