BuildMachinesAndCI.md

Build Machines and Continuous Integration servers

In automated builds, if a file verification fails, there is no point opening up a graphical diff tool to show any errors. At best it is a waste of resources, and at worst, it may stop the build from completing.

So by default, Approval tests will never launch any reporters on supported CI machines. To do this, we use Front Loaded Reporters.

Supported CI systems:

AppVeyor,
GoCD
Jenkins,
TeamCity,
Travis,

^{snippet source / anchor}

The CI detection is based on environment variables, so it may also just work on other systems that we are unaware of:

"CI",
"CONTINUOUS_INTEGRATION",
"GO_SERVER_URL",
"JENKINS_URL",
"TEAMCITY_VERSION"

^{snippet source / anchor}

Or you may be able to set one of these environment variables in the configuration of your CI system, to tell Approval Tests it's running under CI.

However, if your CI system is not supported, and you want to create a custom CI reporter, we suggest you start by looking at CIBuildOnlyReporter.

---

Back to User Guide