action #132332
Updated by okurz 11 months ago
## Observation We see in https://openqa.suse.de/tests/11507412#comments that 8 several `investigate:retry` jobs are commenting back to the original job. ## Acceptance criteria * **AC1:** There is only one comment based on the result of the "retry" job reporting back the investigation results even if multiple jobs have been cloned (like for parallel clusters) ## Suggestions * We don't need to display any other job from an investigation cluster than one corresponding to the original scenario. For example for a salt-master+salt-minion job where the salt-minion job fails we are only interested in results of investigation jobs for the salt-minion testsuite * Find out in the retry job if we are the actual job we're interested in. E.g. we have `salt-master:investigate:retry` and `salt-minion:investigate:retry`. Look into the OPENQA_INVESTIGATE_ORIGIN job data and look at the `TEST` name and compare it to the current TEST, e.g. if "salt-minion" matches the beginning of the string "salt-minion:investigate:retry" then it's the same test, "salt-master" is not the same as "salt-minion:investigate:retry". TEST. If it doesn't match, just return from the post-investigate function. ## Out of scope * Don't care if job links for related jobs of a cluster show up or not, e.g. if the "salt-minion" job failed, it does not matter if a parallel "salt-master" job URL shows up in the original investigate comment or not ## Further details * See #95783 and https://github.com/os-autoinst/scripts/pull/170 for background