Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pipeline that triggers multiple parallel jobs doesn't seem to display failure cause #654

Open
Tommigun1980 opened this issue Feb 17, 2023 · 1 comment

Comments

@Tommigun1980
Copy link

Tommigun1980 commented Feb 17, 2023

Hi and thanks for a great plugin!

I've run into an issue, namely that if you have a pipeline where the invoked project builds several (parallel) builds (such as iOS + Android) then the build monitor seems to only output "X builds have failed" instead of the parsed failure causes.

Maybe downstream failure causes are not fetched?

Could this get fixed, or am I doing something wrong?

Thanks so much!

@Tommigun1980
Copy link
Author

Tommigun1980 commented Feb 22, 2023

Has anyone used the build monitor plugin successfully with any kind of pipeline build that triggers downstream jobs?

The parsed failure causes are visible perfectly normally on the invoking job's page (as fetched from the downstream jobs), but the build monitor only displays 'X builds have failed' instead of the actual failure cause(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant