Output link to Cypress logs in integ-test-opensearch-dashboards

[Swiddis]

Is your feature request related to a problem? Please describe

When tests fail in Jenkins, there's no easy way to locate the logs associated with that run. My understanding is that there's some workflow involving copying various IDs to manually assemble that URL, but I'm not sure where it's documented.

Describe the solution you'd like

It would save a lot of debugging time if there were links to the Cypress logs (and video recordings!) within the Jenkins output itself, a simple message like 2023-12-25 12:00:00 INFO Saved Cypress logs to: https://.../output.log.

Describe alternatives you've considered

Linking to documentation on how to generate the link could also help, without as much string building complexity, but seems roundabout compared to just formatting a string to the correct place directly.

Additional context

No response

[jordarlu]

Hi, @Swiddis , we currently have AUTOCUT issue sent to plugin repos with the test related links, please refer to this opensearch-project/OpenSearch-Dashboards#5506 where you would find the * Test-report manifest:* with all the links to the detail.. hopefully that would resolve this issue? thanks,
cc : @kavilla

[Swiddis]

That looks like it does it, was just not clear that that's where they were... I think the core of the issue is that there's no clear indication within jenkins on how to find the logs, which makes these things feel like tricks that you need to get from someone else. The other approach I know of is to go to the artifacts tab and download the pipeline log, which after a lot of ctrl+f leads to entries like Uploading to ****/integ-test-opensearch-dashboards/2.11.1/6816/linux/x64/tar/test-results/4590/integ-test/observabilityDashboards/with-security/local-cluster-logs/id-1/opensearch-service-logs/gc.log, which combines with the https://ci.opensearch.org/ci/dbc/ link.

It's less about the availability of the logs, theoretically one can find them if they know the right magic, but I think the issue is about discoverability.

[jordarlu]

Thanks for the feedback, @Swiddis , we have the AUTOCUT mentioned at here in opensearch-build repo; and the intention was to provide more visibility and easier access to the logs when people needs it. ( by using the links in those AUTOCUT issues to access to the manifest or the logs on Jenknis ) ; good to know that worked for you.
With that, let me close this issue for now, and plesae feel free to reopen it if necessary. thanks !!

[jordarlu]

Issue should have been addressed with instructions in the comments. thanks!