Currently, all the messages have a "View Logs" link to the prow run, which links to the app: https://prow.ci.../view/gs/${GCS_BUCKET_LOCATION}
However, my main gripe with this is that the page sometimes takes a handful of seconds to load, just to simply click the "Artifacts" link from that page, which is a much faster browsing experience.
There are a number of options to improve this.
Assuming that other users get value out of the default Prow screen, we can leave it in place.
Option 1: Replace "View Logs" link instead of prow UI, directly to the plaintext "build-log.txt" of the run in gcsweb.
This skips the prow UI entirely. If users get value out of this page, then there may be some objections here.
Option 2: Add an "Artifacts" link in the bot's first post.
This link is like the one from the prow page that links directly to the https://gcsweb-ci.../gcs/${GCS_BUCKET_LOCATION}, so a user can skip the Prow UI.
"First post" meaning, the one that posts to the channel with ⚠️ Job XYZ ended with failure. View Logs ⚠️
Goes to: ⚠️ Job XYZ ended with failure. [View Logs](...//prow.ci.../view/gs/...) [Artifacts](...//gcsweb-ci.../gcs/...) ⚠️
A secondary enhancement is closely related:
Feature 2: Add 'Artifacts' link directly to the failed step dir.
This removes the need for a user to navigate the entire repo.
The first message in a thread that might say 🔴 node-density-cni failure 🔴, we can add a link directly to the gcs dir where the build log and artifacts live for that failed step.
Often, the logs' tail that is pasted in the message isn't enough to understand the failure. Rather than increasing the tail length for all messages, we can save the user some time by linking directly to the failed step's artifacts dir.
For example, node-density-cni step's dir for that periodic-ci-openshift-eng-ocp-qe-perfscale-ci-main-aws-5.0-nightly-x86-control-plane-fips-24nodes run looks like: /test-platform-results/logs/periodic-ci-openshift-eng-ocp-qe-perfscale-ci-main-aws-4.21-nightly-x86-payload-control-plane-6nodes/2059153134273433600/artifacts/payload-control-plane-6nodes/openshift-qe-node-density-cni/
Currently, all the messages have a "View Logs" link to the prow run, which links to the app:
https://prow.ci.../view/gs/${GCS_BUCKET_LOCATION}However, my main gripe with this is that the page sometimes takes a handful of seconds to load, just to simply click the "Artifacts" link from that page, which is a much faster browsing experience.
There are a number of options to improve this.
Assuming that other users get value out of the default Prow screen, we can leave it in place.
Option 1: Replace "View Logs" link instead of prow UI, directly to the plaintext "build-log.txt" of the run in gcsweb.
This skips the prow UI entirely. If users get value out of this page, then there may be some objections here.
Option 2: Add an "Artifacts" link in the bot's first post.
This link is like the one from the prow page that links directly to the
https://gcsweb-ci.../gcs/${GCS_BUCKET_LOCATION}, so a user can skip the Prow UI."First post" meaning, the one that posts to the channel with
⚠️ Job XYZ ended with failure. View Logs ⚠️Goes to:
⚠️ Job XYZ ended with failure. [View Logs](...//prow.ci.../view/gs/...) [Artifacts](...//gcsweb-ci.../gcs/...) ⚠️A secondary enhancement is closely related:
Feature 2: Add 'Artifacts' link directly to the failed step dir.
This removes the need for a user to navigate the entire repo.
The first message in a thread that might say
🔴 node-density-cni failure 🔴, we can add a link directly to the gcs dir where the build log and artifacts live for that failed step.Often, the logs' tail that is pasted in the message isn't enough to understand the failure. Rather than increasing the tail length for all messages, we can save the user some time by linking directly to the failed step's artifacts dir.
For example, node-density-cni step's dir for that
periodic-ci-openshift-eng-ocp-qe-perfscale-ci-main-aws-5.0-nightly-x86-control-plane-fips-24nodesrun looks like:/test-platform-results/logs/periodic-ci-openshift-eng-ocp-qe-perfscale-ci-main-aws-4.21-nightly-x86-payload-control-plane-6nodes/2059153134273433600/artifacts/payload-control-plane-6nodes/openshift-qe-node-density-cni/