FIXED
- Fix for TT-4420 with 2 BlazeMeter build steps, Test section just continues to spin
FIXED
- Fixed TT-4354: BlazeMeter Jenkins plugin fails to find file(s) on remote agents
FIXED
- Fixed TT-3886 - Unable to run the test via Jenkins plugin pipeline on remote agents
FIXED
- Fixed TT-4016
FIXED
- Fixed TT-3873 Tests are not getting fetched in the Jenkins BlazeMeter plugin
ADDED
- Implemented webhook configuration for teams and slack
ADDED
- Added loader while loading the tests
FIXED
- Fixed global environment variable issue
ADDED
- Increased API connection timeout
ADDED
- Added No data/ Not set ConditionADDED
- Added master id as a environment variables
FIXED
- Fixed proxy configuration issue
FIXED
- Fixed functional test suite feature video bug
FIXED
- Fixed the version issue related to functional test suite feature
ADDED
- Added functional test suite feature
FIXED
- Users can add or update credentials at folder level
FIXED
- Users can add or update credentials at folder level
FIXED
- fixed public report url issue for functional GUI
FIXED
- Only administer user and manage credentials user can add/update blazemeter credentials
FIXED
- Fixed Functional GUI test shows always success even though failed
ADDED
- upgrade notificationsADDED
- BlazeMeter logo to Report link
ADDED
- Mark build as UNSTABLE if BlazeMeter does not respond with pass or fail (Manage Jenkins -> Configure System -> BlazeMeter Cloud).
If this setting is disabled then build will be marked as FAILED in case BlazeMeter does not respond with pass or fail. If test was not started and this setting is enabled then build will be marked as UNSTABLE
FIXED
: Retry Interceptor. Use Java propertybzm.request.retries.count
for config retries count (by default it is 3).
Will retry only GET
requests in case if response code was not 2** or was throw SocketTimeoutException
ADDED
- Abort job if BlazeMeter has failsCHANGES
- Mark build as unstable if got error: "Not enough available resources"
ADDED
- Validation for test files
FEATURE
- Update test files before running test
Limitations: For Taurus and FunctionalApi tests will set 'Test type': JMeter if file has '.jmx' extension and Taurus - for '.yml' and '.yaml' files. Other 'Test types', please, set in the BlazeMeter application. Supported test types: Taurus, FunctionalApi, JMeter
FIXED
- Search field in Tests dropdown is broken when you add the second BlazeMeter build step
FEATURE
- Change BlazeMeter report link name. By default max report link name length = 35, but you can increase this value using Java System property or Jenkins environment variable "bzm.reportLinkName.length"FEATURE
- Improve set up proxy configuration. By default all slaves will use proxy configuration from Manage Jenkins> Manage Plugins > Advanced. For override proxy setting for any agents need pass Java System property to this agent: -Dproxy.override=true. And if you want use other proxy add -Dhttp.proxyHost= -Dhttp.proxyPort= -Dhttp.proxyUser= -Dhttp.proxyPass= or nothing more for work without proxy
FIXED
- Links to BlazeMeter reports when job has 2 or moreblazeMeterTest
steps. BUG #49195FIXED
-bzm-log
file contains logs only from one MasterCHANGES
- updateblazemeter-api-client
dependency version from1.5
to1.8
(changelog)
FEATURE
: Search tests inTests
dropdownCHANGES
: Migration to blazemeter-api-client- complete old keys deprecation;
CHANGES
: Combiningbzm-log
file withhttp-log
file; Resulting file will have namebzm-log
.
See Logging for the file location.FIXED
: Snippet generator for Jenkins pipeline.CHANGES
: JDK 7 back-compatibility.
Verification environment: Jenkins 2.89.3
FEATURE
:workspace
selector to job configuration: users can select BlazeMeter workspace to fetch tests from.FEATURE
:average throughput
and90% response time
metrics to aggregate report;- Aggregate report values are rounded to 2 decimal places;
Verification environment: Jenkins 2.73.2 LTS
FEATURE
: support new BlazeMeter api-keys
Verification environment: Jenkins 2.60.2 LTS
NOTE: While plugin still can work with old keys, we strictly recommend to migrate to new api-keys.
- Pipeline support;
FEATURE
: support Job DSL;- Migration to OkHttp client;
FEATURE
: sort test drop-down alphabetically;FEATURE
: do 3 re-tries if received 500 from server;
Added
: full master/slave support - BZM job will be completely executed at JVM of selected node(master or slave).
-
CHANGES
: Using native jenkins interface for proxy configuration. Go to "Manage Jenkins" -> "Manage Plugins" ->"Advanced".
These proxy settings are used both by jenkins & plugin. -
FEATURE
: support master/slave configuration -
FEATURE
: doing 3 retries while downloading jtl report: connection timeout - 10,30,90 s. -
FEATURE
: ability to send jmeter-properties to session; -
FEATURE
: ability to send report notes to master session; -
FEATURE
: ability to set path to jtl report(jenkins variables are respected) -
FEATURE
: ability to set path to junit report(jenkins variables are respected) Last four settings are available under "Advanced" button.
FEATURE
: Support proxy server. Proxy setting are available in "Manage Jenkins" -> "Configure System".
FIXED
: Set default value for 'serverUrl';FIXED
: Default value will be used if 'serverUrl' was left empty;
FIXED
: Download reports if test finished with failures;FIXED
: Empty userKey validation;FIXED
: Build will be failed if test was terminated on booting stage;
FIXED
: minor changes;
FEATURE
: Plugin now supports Blazemeter 3.0 testsFEATURE
: Plugin now supports JSON tests
FIXED
: Aggregate results more accurate, and handle errors better.
FIXED
: API calls handle errors better.
- Release with minor changes.
FEATURE
: Plugin now supports proxy settings defined in: Jenkins/plugins/advanced.
FEATURE
: Multiple UserKeys can be inserted via the "Credentials Plugin".
FIXED
: Main JMX file uploads correctly.
FEATURE
: Binary files now available for upload in data directory.FIXED
: Main JMX file now set correctly.FIXED
: Some graphical tweaks to the report page.CHANGES
: Test duration override has 3 hours set by default, not 20 minutes.CHANGES
: Test list populated by last updated.CHANGES
: Report page has no need for the user to be logged in to BlazeMeter.
The First release.