JENKINS-26107 suggests a label for a block, but a (generally static) label set at the start, whereas this is mainly about adding summary information at the end. So that would probably have to be a different step.

JENKINS-26523 notes that the ability to set Run.result may be useful.

A related request was for a stage to be marked with a custom icon, to indicate what kind of stage this way, or to add some key/value pairs such as name of environment we deployed to.

Okay, to try & better explain what we're trying to achieve, here's our current implementation, which is split into three parts:

Custom logic in the job shell script to annotate results

roughly speaking, this looks like:

STEP="System.Security-4.5"
STARTTIME=`date +%s`
echo "*** start: ${STEP}"
${TIMEOUTCMD} --signal=ABRT --kill-after=60s 5m make -w -C mcs/class/System.Security run-test TEST_HARNESS_FLAGS=-labels PROFILE=net_4_x && echo -e "*** end($(echo $(date +%s) - ${STARTTIME} | bc)): ${STEP}: \\e[42mPassed\e[0m" || echo -e "*** end($(echo $(date +%s) - ${STARTTIME} | bc)): ${STEP}: \\e[43mUnstable\e[0m"

This assigns blocks of tests (roughly equivalent to Pipeline stages) to run together, with a common timeout, and either a "pass" status or an "unstable" status (unstable indicating this block had a non-zero exit status, but that execution of the script should continue). For steps where failure should be deemed critical, the colour code is red instead of yellow, status text says "failed", and there's some extra exit 1's thrown in.

Groovy script to parse the build log and generate a job status table

Pretty much just builds an HTML <table>, pairing "*** start" and "*** end" lines to build the table structure and write the execution time, and adding the most recent test runner output as an at-a-glance summary

Aggregate the data from multiple jobs in a giant table, with a custom plugin

this gives the most dense data view we can manage - 76 steps, 5 architectures, with an at-a-glance look for developers of "did I break tests grouped into X on architecture Y", or "is builder Z misbehaving and in need of attention"

I would love to move as much of this crap into a Jenkinsfile as possible. Certainly parts 1 and 2 of the above seem theoretically feasible to me, but there are gaps that means I'd just end up emulating bash really badly in Groovy, rather than taking advantage of Pipeline features (because the Pipeline versions are missing things)