|
|
||
|---|---|---|
| .github/ISSUE_TEMPLATE | ||
| containers | ||
| docs | ||
| Jenkins | ||
| kubernetes | ||
| phabricator-proxy | ||
| scripts | ||
| .editorconfig | ||
| .gitignore | ||
| k8s_config | ||
| LICENSE | ||
| local_setup.sh | ||
| README.md | ||
Overview
This repository contains the configuration files for the pre-merge checks for the LLVM project. This github project contains the documentation and the server configuration cluster of build machines that are used to check all incoming commits to the LLVM project.
User documentation
If you are interested in a high-level overview and how to best use the tool see docs/user_doc.md
Cluster overview
The cluster consists of these services:
- Jenkins build server: http://jenkins.llvm-merge-guard.org
- a set of Jenkins agents running the builds
- an nginx server with the build results/logs http://results.llvm-merge-guard.org
Jenkins-Phabricator integration
The Jenkins-Phabricator is based on the instructions provided with the Phabricator-Jenkins Plugin.
On the Phabricator side these things were configured:
- the Harbormaster build plan
- the Herald rule
- the merge_guards_bot user writing the comments
On the Jenkins side:
- in the Jenkins configuration page as explained in the instrucitons
- in the build job
- The Phabricator pluging is not used, as it's not flexible enough. Rather Phabricator just triggers the build via an HTTP request. The
arc patchoperations by scripts. The build feedback is also uploaded by scripts via the harbormaster.sendmessage and differential.revision.edit APIs.
There is no backup of the credentials. If you need to change it, generate a new one and update it in Jenkins and Phabricator.
Additional Information
- Playbooks for installing/upgrading agents and testing changes.
- User documentation
- Log of the service operations
License
This project is licensed unter the "Apache 2.0 with LLVM Exception" license. See LICENSE for details.