61bf0db817
Jenkins has a limitation where you can't mark a step a failure, it has to *fail* to be reported as such. This means that running multiple tests, and reporting a failure if any of those tests fail is not possible. We run into this with the normal test run + the docs tests; where we currently don't show a red result in the UI if any of those fail. So incorporate the test-docs step into xharness, so that we only have one thing to in the Jenkinsfile, which makes it possible for us to fail the test run step properly. This also required a few upgrades to xharness to get more info for pull requests, since the logic to enable the docs tests is a bit more complicated than anything else we have (if the current branch (or the target branch for a PR) is 'master' AND xamarin mode is enabled). |
||
---|---|---|
.. | ||
.gitignore | ||
Jenkinsfile | ||
Makefile | ||
README.md | ||
add-commit-comment.sh | ||
add-commit-status.sh | ||
build-api-diff.sh | ||
build-package.sh | ||
build.sh | ||
compare.sh | ||
fetch-pr-labels.sh | ||
prepare-packaged-macos-tests.sh | ||
productsign.sh | ||
provision-deps.sh | ||
publish-results.sh | ||
run-tests.sh | ||
utils.groovy | ||
vsts-device-tests-set-status.sh |
README.md
Jenkins
This directory contains all the scripts to be executed as steps in the jenkins build bots for each of the PR in the project. The expected order in which they have to be executed is as follows:
- provision-deps.sh : Downloads and installs the project dependencies.
- build.sh : Builds the project.
- run-tests.sh : Runs the tests.
- build-api-diff.sh : Builds the API diff.
Jenkinsfile
This file contains the logic to run on our internal Jenkins, available here: http://xamarin-jenkins/blue/organizations/jenkins/macios/activity
The Jenkins job is a multi-branch pipeline job, it will execute in the following conditions:
- For all branches in the xamarin org (not forks) that has a jenkins/Jenkinsfile file.
- For all pull requests from people with write access (also conditional on having a jenkins/Jenkinsfile file).
In very broad strokes, the Jenkins job will:
-
Checkout xamarin-macios
-
Build
-
Create packages, upload them to Azure and publish the links to the packages as GitHub statuses.
-
Run our test suite.
-
Run selected Xamarin.Mac tests on all macOS versions we support. This is done in parallel with the normal test run.
If a particular macOS version must be excluded temporarily from testing, search Jenkinsfile for
excludedOSes
and follow the instructions you'll find.