2016-09-21 17:46:00 +03:00
|
|
|
#!/bin/bash -e
|
|
|
|
|
|
2018-05-29 18:03:54 +03:00
|
|
|
cd "$(dirname "${BASH_SOURCE[0]}")/.."
|
|
|
|
|
WORKSPACE=$(pwd)
|
|
|
|
|
|
2018-04-05 08:37:08 +03:00
|
|
|
report_error ()
|
|
|
|
|
{
|
2018-05-29 18:03:54 +03:00
|
|
|
printf "🔥 [Failed to create API Diff](%s/console) 🔥\\n" "$BUILD_URL" >> "$WORKSPACE/jenkins/pr-comments.md"
|
2018-04-05 08:37:08 +03:00
|
|
|
}
|
|
|
|
|
trap report_error ERR
|
|
|
|
|
|
2018-06-26 16:50:54 +03:00
|
|
|
# SC2154: ghprbPullId is referenced but not assigned.
|
|
|
|
|
# shellcheck disable=SC2154
|
|
|
|
|
if test -n "$ghprbPullId" && ./jenkins/fetch-pr-labels.sh --check=skip-public-jenkins; then
|
|
|
|
|
echo "Skipping API diff because the label 'skip-public-jenkins' was found."
|
|
|
|
|
exit 0
|
|
|
|
|
fi
|
|
|
|
|
|
2016-09-21 17:46:00 +03:00
|
|
|
export BUILD_REVISION=jenkins
|
|
|
|
|
make -j8 -C tools/apidiff jenkins-api-diff
|
2018-04-05 08:37:08 +03:00
|
|
|
|
Add support for building on Jenkins. (#4159)
Add support for building on internal Jenkins.
Jenkins has been configured to build every branch on xamarin/xamarin-macios that contains a `jenkins/Jenkinsfile`, which means it will start working as soon as this PR is merged.
Results will be posted as statuses on each commit, which can be viewed using the url `https://github.com/xamarin/xamarin-macios/commits/<branch>`:
* The `continuous-integration/jenkins/branch` status links to the jenkins job.
* The other two are XI and XM packages (the `Jenkins-` prefix will be removed once we officially switch from Wrench to Jenkins).
More detailed information will be added as a comment to each commit, which can be seen by clicking on the commit and scrolling to the bottom (url of the format `https://github.com/xamarin/xamarin-macios/commit/<sha1>`)
Unfortunately GitHub does not display the commit statuses when viewing a single commit, so to view those statuses you'll have to view the list of commits (the `/commits/` url). Tip: it's possible to use `<sha1>` instead of `<branch>` (and vice versa for that matter) if you're interested in the statuses of a particular commit.
Pull requests will also be built (only from contributors with write access), but by default nothing will be done (the job will exit immediately, although a green check mark will still show up). Jenkins will **not** add a comment in the pull request in this case.
However, if the label `build-package` [1] is set for a pull request, the internal jenkins job will run (it will do everything except the local xharness test run: this includes creating and publishing packages, creating various diffs, run tests on older macOS versions, test docs, etc). A detailed comment will also be added to the pull request (see below for multiple examples), which means that there will be two Jenkins comments: one for the public Jenkins which builds every PR, and one for the internal Jenkins [2].
[1] I don't quite like the name of the label, because it doesn't get even close to explain all that will actually happen, but `run-on-internal-jenkins-and-create-package` is a bit too long IMHO... Also it's non-obvious that this is the label to apply if the reason for executing on the internal jenkins is some other reason (for instance to test a maccore bump). Other ideas:
* `run-internal-jenkins`: doesn't make it obvious that a package will be created (which is probably the most common reason to want to run on internal jenkins)
* We could have multiple labels that mean the same thing: `build-package`, `internal-build`, `run-internal-jenkins`, etc, but it's redundant and I don't quite like it either.
* Any other ideas?
[2] I'm noticing now that these two look quite similar and this might end up confusing (the main difference is that the comment from the public jenkins will say **Build success/failure** and **Build comment file:** at the top. If something goes wrong the failure will also show up differently). Should this be made clearer?
2018-06-05 02:40:16 +03:00
|
|
|
if [[ "x$1" == "x--publish" ]]; then
|
|
|
|
|
URL_PREFIX=$(./jenkins/publish-results.sh | grep "^Url Prefix: " | sed 's/^Url Prefix: //')
|
|
|
|
|
URL="$URL_PREFIX/api-diff/index.html"
|
|
|
|
|
else
|
|
|
|
|
URL="$BUILD_URL/API_20diff_20_28from_20stable_29"
|
|
|
|
|
fi
|
|
|
|
|
|
|
|
|
|
printf "✅ [API Diff (from stable)](%s)\\n" "$URL" >> "$WORKSPACE/jenkins/pr-comments.md"
|
