I see. While I can appreciate the general utility, personally I think expanding and hunting through the console logs might be a bit of a clunky approach to this. Most of the (very legacy) JavaScript that does this (pre packing) is
here (
console_log_*.js) so if you feel like figuring it out and submitting a PR........
As another alternative, what about producing a "custom artifact" which is just a trivial HTML page with your collection of links/useful resources related to the given build?
You could have a task at the end of each build job which just does the equivalent of the below (or use some basic templating language if you'd rather)
cat <<-EOF > useful-links.html
<html>
<head><title>Useful Links</title></head>
<body>
<a href="https://my-server/dependency-report-${GO_PIPELINE_COUNTER}-${GO_STAGE_COUNTER}.html">Dependency Check Report</a>
<a href="https://my-server/deploy-failure-faq/">Common failure causes</a>
</body>
</html>
EOF
echo "Take a look at the 'Useful Links' tab in GoCD to help you understand possible reasons for any failures 🥳"
If you
- set the task to runIf: always (so it runs on failures too)
- artifact that trivial useful-links.html
- create a custom tab for it
... folks might get used to checking that tab as an alternative to the logs. :-)
-Chad