Fix: Robot Framework logging 25/37425/2
authorEric Ball <eball@linuxfoundation.org>
Thu, 13 Oct 2022 21:35:41 +0000 (14:35 -0700)
committerEric Ball <eball@linuxfoundation.org>
Mon, 17 Oct 2022 18:53:03 +0000 (11:53 -0700)
The builder should be ubuntu, and the logging script has been
modified to include robot logs if found.

Change-Id: I4fedf0b8b36dfb56cc43546ab3d1f4fc7c63562c
Signed-off-by: Eric Ball <eball@linuxfoundation.org>
jjb/hicn/hicn.yaml
jjb/scripts/post_build_deploy_archives.sh

index 9d1dabe..000e9e5 100644 (file)
     name: "hicn-verify-functest-{stream}-{os}-{executor-arch}"
 
     project-type: freestyle
-    node: "centos7-docker-4c-4g"
+    node: "ubuntu2004-docker-4c-4g"
     concurrent: true
 
     properties:
index 02a56f1..a332f21 100755 (executable)
@@ -19,6 +19,10 @@ set +e  # Do not affect the build result if some part of archiving fails.
 WS_ARCHIVES_DIR="$WORKSPACE/archives"
 BUILD_ENV_LOG="$WS_ARCHIVES_DIR/_build-enviroment-variables.log"
 
+if curl --output robot-plugin.zip "$BUILD_URL/robot/report/*zip*/robot-plugin.zip"; then
+    unzip -d ./archives robot-plugin.zip
+fi
+
 # Generate gdb-command script to output vpp stack traceback from core files.
 gdb_cmdfile="/tmp/gdb-commands"
 cat >$gdb_cmdfile <<'__END__'