buildbot_config/worker/submit_result

#!/bin/bash
# ReactOS BuildBot Build Scripts
# submit_result - Call Testman's BuildBot Aggregator script to collect the regression-testing output by sysreg.
#
# Parameter $1 - BuildBot Build number of the ReactOS build that has been tested.
# Parameter $2 - BuildBot "reason" property.
# Parameter $3 - JIRA Attachment ID of the patch file (this parameter can be evaluated as $ATTACHMENT_ID inside config.inc to set different sourceids for regular and patched builds)
BUILDNO="$1"
REASON="$2"
ATTACHMENT_ID="$3"
source ../../config.inc

if [ "${BUILDNO}" = "" ]; then
	echo "Please specify the build number!"
	exit 1
fi

echo "* Transferring winetest results for build ${BUILDNO}."
echo "* Using builder $TESTMAN_BUILDER."

COMMENT="Build ${BUILDNO}"
if [ "${ATTACHMENT_ID}" != "" ]; then
	COMMENT+=", ID: ${ATTACHMENT_ID}"
fi
if [ "${REASON}" != "" -a "${REASON}" != "None" ]; then
	COMMENT+=", Reason: ${REASON}"
fi

TESTMAN_OUT=`wget -q -O - "https://reactos.org/testman/webservice/buildbot_aggregator.php?sourceid=$TESTMAN_ID&password=$TESTMAN_PASS&builder=$TESTMAN_BUILDER&platform=0&build=$1&comment=$COMMENT"`
echo "$TESTMAN_OUT"

[ "$TESTMAN_OUT" = "OK" ] && exit 0 || exit 1
[BUILDBOT] Time to get the BuildBot SVN files back on track. These are the (partly redacted) build scripts from the Debug Buildslave (Linux_AMD64_1). The idea is to have one set of shared scripts for all our Linux-based Buildslaves in the future. svn path=/trunk/buildbot/; revision=2108 2014-05-20 07:08:21 +00:00			`#!/bin/bash`
[BUILDBOT] Instead of distinguishing between regular Buildslaves and Patchbots, let's make all Buildslaves accept patches if you enter something in the ID field. This also highly simplifies my README file :) Thanks to Hermès for the idea! svn path=/trunk/buildbot/; revision=2189 2015-02-26 23:13:12 +00:00			`# ReactOS BuildBot Build Scripts`
[BUILDBOT] Document and streamline our build scripts. With shared and per-builder settings, we can now have a buildslave with multiple builders. More configuration settings also allow these scripts to be finally deployed on all our Linux buildslaves. svn path=/trunk/buildbot/; revision=2146 2014-10-25 17:26:19 +00:00			`# submit_result - Call Testman's BuildBot Aggregator script to collect the regression-testing output by sysreg.`
			`#`
			`# Parameter $1 - BuildBot Build number of the ReactOS build that has been tested.`
[BUILDBOT] Fully adapt our BuildBot setup to the upcoming Git migration. - Get a clean version of the source from git://git.reactos.org on every commit and use "git apply" to apply JIRA patches. - Introduce the naming scheme "reactos-$TYPE-$REVISION_SUFFIX-$UPLOAD_SUFFIX" for all created ISO files. * $TYPE can be bootcd, livecd, bootcdregtest. * $REVISION_SUFFIX is the output of "git describe" (e.g. "0.4.7-dev-53-gc2b45a7"), followed by "patch$ID" if a JIRA patch is applied. * $UPLOAD_SUFFIX is the architecture, compiler, OS, build type identification of the builder. An example filename that includes everything: "reactos-bootcd-0.4.7-dev-53-gc2b45a7-patch2518-x86-msvc-win-dbg.iso" - Allow passing arbitrary parameters to CMake in the "configure" script. This is used to pass "-DENABLE_ROSTESTS=1". - Rename "patching" to "prepare_source", because it also prepares the revision suffix now. - Introduce "get_suffix" to feed the generated filename suffix back to a BuildBot property (using BuildBot's SetPropertyFromCommand). - Create one "latest" symlink per upload suffix in "uploadiso". - Use the "comment" parameter I will introduce in my next Testman commit to supply an arbitrary comment in "submit_result". Add the JIRA Attachment ID and Reason for patched builds on Timo's request. - Remove the "revert" step and slim down "clean". A tidy cleanup of the source directory is now being done by the Git build step. - Remove the "build_host_tools" script and ROS_NO_HOST_TOOLS_REV. You can't build the old revisions with the Git-adapted scripts. - Work in $ROS_OUTPUT instead of $ROS_OUTPUT/reactos. - Introduce the UPLOAD_REGTESTCD configuration variable to decide whether to upload the bootcdregtest in "regtestcd". - Allow us to either download a bootcdregtest or use the latest one from the source folder in "regtest". - Build rosapps and rostests on the GCCWin and MSVC2010 builder. These don't upload anything, so we can check if the entire tree builds correctly without wasting ISO storage space. svn path=/trunk/buildbot/; revision=2351 2017-09-16 15:21:08 +00:00			`# Parameter $2 - BuildBot "reason" property.`
			`# Parameter $3 - JIRA Attachment ID of the patch file (this parameter can be evaluated as $ATTACHMENT_ID inside config.inc to set different sourceids for regular and patched builds)`
Unify `run_rostests` and `submit_result` 2023-02-02 12:01:34 +00:00			`BUILDNO="$1"`
			`REASON="$2"`
			`ATTACHMENT_ID="$3"`
[BUILDBOT] Time to get the BuildBot SVN files back on track. These are the (partly redacted) build scripts from the Debug Buildslave (Linux_AMD64_1). The idea is to have one set of shared scripts for all our Linux-based Buildslaves in the future. svn path=/trunk/buildbot/; revision=2108 2014-05-20 07:08:21 +00:00			`source ../../config.inc`

Unify `run_rostests` and `submit_result` 2023-02-02 12:01:34 +00:00			`if [ "${BUILDNO}" = "" ]; then`
[BUILDBOT] Time to get the BuildBot SVN files back on track. These are the (partly redacted) build scripts from the Debug Buildslave (Linux_AMD64_1). The idea is to have one set of shared scripts for all our Linux-based Buildslaves in the future. svn path=/trunk/buildbot/; revision=2108 2014-05-20 07:08:21 +00:00			`echo "Please specify the build number!"`
			`exit 1`
			`fi`

Unify `run_rostests` and `submit_result` 2023-02-02 12:01:34 +00:00			`echo "* Transferring winetest results for build ${BUILDNO}."`
[BUILDBOT] Time to get the BuildBot SVN files back on track. These are the (partly redacted) build scripts from the Debug Buildslave (Linux_AMD64_1). The idea is to have one set of shared scripts for all our Linux-based Buildslaves in the future. svn path=/trunk/buildbot/; revision=2108 2014-05-20 07:08:21 +00:00			`echo "* Using builder $TESTMAN_BUILDER."`
[BUILDBOT] - Clean any existing "modules/rostests_disabled" before renaming "modules/rostests" to it. - Propagate more possible errors during "patching" and "regtestcd" phases. - Check for "OK" from Testman when submitting a result, indicate an error otherwise. svn path=/trunk/buildbot/; revision=2133 2014-08-13 06:54:34 +00:00
Unify `run_rostests` and `submit_result` 2023-02-02 12:01:34 +00:00			`COMMENT="Build ${BUILDNO}"`
			`if [ "${ATTACHMENT_ID}" != "" ]; then`
			`COMMENT+=", ID: ${ATTACHMENT_ID}"`
			`fi`
			`if [ "${REASON}" != "" -a "${REASON}" != "None" ]; then`
			`COMMENT+=", Reason: ${REASON}"`
[BUILDBOT] - Clean any existing "modules/rostests_disabled" before renaming "modules/rostests" to it. - Propagate more possible errors during "patching" and "regtestcd" phases. - Check for "OK" from Testman when submitting a result, indicate an error otherwise. svn path=/trunk/buildbot/; revision=2133 2014-08-13 06:54:34 +00:00			`fi`

[BUILDBOT] Fully adapt our BuildBot setup to the upcoming Git migration. - Get a clean version of the source from git://git.reactos.org on every commit and use "git apply" to apply JIRA patches. - Introduce the naming scheme "reactos-$TYPE-$REVISION_SUFFIX-$UPLOAD_SUFFIX" for all created ISO files. * $TYPE can be bootcd, livecd, bootcdregtest. * $REVISION_SUFFIX is the output of "git describe" (e.g. "0.4.7-dev-53-gc2b45a7"), followed by "patch$ID" if a JIRA patch is applied. * $UPLOAD_SUFFIX is the architecture, compiler, OS, build type identification of the builder. An example filename that includes everything: "reactos-bootcd-0.4.7-dev-53-gc2b45a7-patch2518-x86-msvc-win-dbg.iso" - Allow passing arbitrary parameters to CMake in the "configure" script. This is used to pass "-DENABLE_ROSTESTS=1". - Rename "patching" to "prepare_source", because it also prepares the revision suffix now. - Introduce "get_suffix" to feed the generated filename suffix back to a BuildBot property (using BuildBot's SetPropertyFromCommand). - Create one "latest" symlink per upload suffix in "uploadiso". - Use the "comment" parameter I will introduce in my next Testman commit to supply an arbitrary comment in "submit_result". Add the JIRA Attachment ID and Reason for patched builds on Timo's request. - Remove the "revert" step and slim down "clean". A tidy cleanup of the source directory is now being done by the Git build step. - Remove the "build_host_tools" script and ROS_NO_HOST_TOOLS_REV. You can't build the old revisions with the Git-adapted scripts. - Work in $ROS_OUTPUT instead of $ROS_OUTPUT/reactos. - Introduce the UPLOAD_REGTESTCD configuration variable to decide whether to upload the bootcdregtest in "regtestcd". - Allow us to either download a bootcdregtest or use the latest one from the source folder in "regtest". - Build rosapps and rostests on the GCCWin and MSVC2010 builder. These don't upload anything, so we can check if the entire tree builds correctly without wasting ISO storage space. svn path=/trunk/buildbot/; revision=2351 2017-09-16 15:21:08 +00:00			TESTMAN_OUT=`wget -q -O - "https://reactos.org/testman/webservice/buildbot_aggregator.php?sourceid=$TESTMAN_ID&password=$TESTMAN_PASS&builder=$TESTMAN_BUILDER&platform=0&build=$1&comment=$COMMENT"`
			`echo "$TESTMAN_OUT"`

			`[ "$TESTMAN_OUT" = "OK" ] && exit 0 \|\| exit 1`