No description

Find a file

Mikhail Goncharov 89d294ef42 return exit status of ninja command - Fix for #207. Previously grep was exiting with 1 and fail build if all lines from ninja are filtered. Also piping might hide exit code of the initial command. Now "tee" and "grep" is implemented on python level and we get exit code of the original command. - Fixed default value of "scripts_branch", print scripts commit; - Added option to filter ninja output (on by default as before). - Copied cache usege reporting and error handling from "master" branch build to diff checks (useful for debugging).		2020-07-10 19:35:29 +02:00
.github/ISSUE_TEMPLATE	Update bug_report.md	2019-12-11 16:06:13 +01:00
containers	add perl to windows image	2020-07-08 10:25:05 +02:00
docs	Merge pull request #204 from mtrofin/patch-1	2020-07-07 15:12:23 +02:00
Jenkins	changed result url for windows builds	2020-05-27 11:19:02 +02:00
kubernetes	Deployment changes	2020-06-17 09:46:42 +02:00
phabricator-proxy	wording	2020-06-04 15:04:42 +02:00
scripts	return exit status of ninja command	2020-07-10 19:35:29 +02:00
.editorconfig	building with buildkite	2020-05-25 16:42:40 +02:00
.gitignore	ignoring .DS_Store	2020-05-06 12:44:16 +02:00
k8s_config	added windows cluster	2020-02-03 12:41:54 +01:00
LICENSE	added license	2019-10-04 14:31:57 +02:00
local_setup.sh	Add 2 more jenkins nodes.	2019-10-14 12:22:25 +02:00
README.md	Update README.md	2020-05-11 09:55:53 +02:00

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

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 patch operations 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

License

This project is licensed unter the "Apache 2.0 with LLVM Exception" license. See LICENSE for details.