Skip to content
CI system for premerge-testing in LLVM project
Shell Python Groovy Dockerfile HTML
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
Jenkins fixed stage name Nov 18, 2019
containers upgraded to python3, added dependencies for more projects Nov 13, 2019
docs added section on requirements Nov 18, 2019
kubernetes moved auth file out of the source tree Nov 8, 2019
scripts do not fail if log can't be crated Nov 18, 2019
.gitignore initial import of configuration files Oct 4, 2019
LICENSE added link to user documentation Nov 4, 2019
k8s_config configuration for new GCP project (#31) Oct 28, 2019 Add 2 more jenkins nodes. Oct 14, 2019


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/

Pre-merge check vision for end of 2019

Maria is a developer working on a new idea for the LLVM project. When she submits a new diff to Phabricator (or updates an existing diff), the pre-merge checks are triggered automatically in the cloud. The pre-merge checks run in one configuration (amd64, Debian Testing, clang8) and comprise these steps:

  • run CMake
  • compile and link
  • run check-all
  • run clang-format and clang-tidy

Once a check is completed, the results are are attached to the Diff in Phabricator so that Maria is notified automatically with the results. Now she can check if the pre-merge checks passed and fix things as required. This way she does not have to run all checks on her local machine by hand. The first results are available within 2 hours of a change, but typically within 30 minutes.

As the pre-merge check cover the easy parts, a human reviewer can focus on the parts that the machine cannot cover. The pre-merge checks are optional, so a reviewer can also decide to ignore them if they do not work, take too long, or do not make sense. The build bots are still in place as they cover a much wider range of checks on the different platforms. So after Maria’s change has landed, the build bots might still find more bugs that were not found in the pre-merge checks. The number should be lower than what we have today though.


During the LLVM developer meeting in Octover 2019, this was the raodmap we discussed:

  • Until mid of November: preparation of the infrastructure for the beta testing
  • Mid of November:
    • Announcement of the public beta testing phase on the LLVM mailing list.
    • Interested users are white-listed on the Herald rule.
  • Until Januar: Beta testing for interested users.
  • In January:
    • Based on the feedback so far: enable pre-merge tests for all users.
    • Users can opt-out via a black-list in the Herald rule.
    • Start discussion with LLVM foundation on a permanent setup/maintenance for the pre-merge tests.

This roadmap is also reflected in the Milestones.

Cluster overview

The cluster consists of these services:

deployment diagram

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:

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


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

You can’t perform that action at this time.