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

Compatible with flexible publisher #59

Merged
merged 1 commit into from Apr 15, 2016
Merged

Conversation

hfufu
Copy link
Contributor

@hfufu hfufu commented Apr 15, 2016

The original parser lookup in ifSummarizerParsedUsed is not comptaible with flexible publisher, because the performance publisher is not directly in buildAction.getBuild().getProject().getPublishersList(), but wrapped inside publisher list of flexible publisher. It will result in NPE because buildAction.getBuild().getProject().getPublishersList().get(PerformancePublisher.class) return null.

We can just simply look up with buildAction.getParserByDisplayName directly instead of looping the project publisher list to check for JmeterSummarizer and Iago parser. The parser list is already there in buildAction. This way the code is simpler, and we can avoid complicated lookup when this publisher is under flexible publisher.

The original parser lookup in ifSummarizerParsedUsed is not comptaible with flexible publisher, because the performance publisher is not directly in buildAction.getBuild().getProject().getPublishersList(), but wrapped inside publisher list inside flexible publisher. It will result in NPE because buildAction.getBuild().getProject().getPublishersList().get(PerformancePublisher.class) return null.

We can just simply look up with buildAction.getParserByDisplayName directly instead of looping the project publisher list to check for JmeterSummarizer and Iago parser. The parser list is already there in buildAction. This way the code is simpler, and we can avoid complicated lookup when this publisher is under flexible publisher.
@undera undera merged commit d47e404 into jenkinsci:master Apr 15, 2016
@lcustodio
Copy link

Hi @undera @hfufu !
Is there a JIRA issue related to this change? If so, the bot looks for [FIXED JENKINS-1234] in order to close it.

It's really good to see the project having attraction again. :)

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