-
Notifications
You must be signed in to change notification settings - Fork 594
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
Introduce filterRegex parameter for performance report publisher #4555
Conversation
Add filterRegex parameter to jmeter configuration. Set it to an empty string as generated from pipelinesyntax reference in jenkins
Add the filterRegex param to the publishJmeterReport plugin in testPublishResults
/it-go |
@CCFenner @anilkeshav27 Can someone take a look at this ? |
@ashlymat Can someone from the piper community please help merge this change? |
@sumeetpatil @OliverNocon Can someone from the code owners please look at this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a quick question would we need to add these
@@ -481,6 +481,7 @@ steps: | |||
active: false | |||
jmeter: | |||
pattern: '**/*.jtl' | |||
filterRegex: '' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a quick question this filterRegex
would also needed to be added to the piper defaults when using the sap specefic defaults ?. that comes from a different repo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@anilkeshav27 It probably should be. But why is a step loading values from two different configs ? Aren't certain steps meant to be coming from the piper-lib-os and not the internal one ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Kudos, SonarCloud Quality Gate passed! |
/it-go |
…#4555) * Update default_pipeline_environment.yml Add filterRegex parameter to jmeter configuration. Set it to an empty string as generated from pipelinesyntax reference in jenkins * Update testsPublishResults.groovy Add the filterRegex param to the publishJmeterReport plugin in testPublishResults * Update documentation to include filterRegex --------- Co-authored-by: Anil Keshav <[email protected]>
* Update default_pipeline_environment.yml Add filterRegex parameter to jmeter configuration. Set it to an empty string as generated from pipelinesyntax reference in jenkins * Update testsPublishResults.groovy Add the filterRegex param to the publishJmeterReport plugin in testPublishResults * Update documentation to include filterRegex --------- Co-authored-by: Anil Keshav <[email protected]>
…#4555) * Update default_pipeline_environment.yml Add filterRegex parameter to jmeter configuration. Set it to an empty string as generated from pipelinesyntax reference in jenkins * Update testsPublishResults.groovy Add the filterRegex param to the publishJmeterReport plugin in testPublishResults * Update documentation to include filterRegex --------- Co-authored-by: Anil Keshav <[email protected]>
Changes
Step
testsPublishResults
use the performance plugin from jenkins to publish jmeter reports. It is possible to set thresholds per test and fail pipelines if they exceed. This feature was broken as the parameterfilterRegex
was not defined in piper-defaults and was always evaluating tonull
.Error observed in pipelines before the change
With these changes, the plugin is able to set the threshold and parse the file. Working output below
This step and the feature from the performance plugin is actively used by our teams to notify on performance degradation for our services.