From a8e282b0c0e17fff4a16fceb2bb65bb57797ae97 Mon Sep 17 00:00:00 2001 From: Eric Engestrom Date: Mon, 5 May 2025 16:01:50 +0200 Subject: [PATCH] ci/ci-tron: print all the variables This makes it easier to debug inheritance issues like the one fixed earlier in this series, and makes it easier to reproduce a job without needing more than looking at the job log. Part-of: --- .gitlab-ci/test/gitlab-ci.yml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/.gitlab-ci/test/gitlab-ci.yml b/.gitlab-ci/test/gitlab-ci.yml index 3ed15d00111..a4b49ccff87 100644 --- a/.gitlab-ci/test/gitlab-ci.yml +++ b/.gitlab-ci/test/gitlab-ci.yml @@ -435,6 +435,11 @@ yaml-toml-shell-py-test: # Open a section that will be closed by b2c echo -e "\n\e[0Ksection_start:`date +%s`:b2c_kernel_boot[collapsed=true]\r\e[0K\e[0;36m[$(cut -d ' ' -f1 /proc/uptime)]: Submitting the CI-tron job and booting the DUT\e[0m\n" + # Print all the variables, for debugging and for easier reproducibility. + # Note: a better solution will be implemented soon, but this is enough + # for now. + printenv + # Anything our job places in results/ will be collected by the # Gitlab coordinator for status presentation. results/junit.xml # will be parsed by the UI for more detailed explanations of