Releases: naver/ngrinder
Releases · naver/ngrinder
ngrinder-3.5.9-p1-20240613
Changes
- Fix security vulnerability
ngrinder-3.5.9
ngrinder-3.5.8
- Changes
- Shows error message when running without tmpdir property
ngrinder-3.5.7
ngrinder-3.5.6
-
Changes
- Bump OSHI up to 6.1.6 to support M1 arch
- Bump select2 version up
- Change Jython test thread shutdown log level
- Change nabble forum URL
- Fix scm-manager maven repo URL
- Remove ES-Check gradle task
-
Bug fix
- #897 Fix the script content is lost after validation check
ngrinder-3.5.5-p1
- Bug fix
- #804 Fix that perftest detail report does not rendered properly if logout
ngrinder-3.5.5
- Changes
- Support controller subregion
- In cluster mode, you can configure subregion to manage agents in different context
- See Controller Subregion In Cluster Mode
- Support multipart request in new HTTP client
- See Sample code
- Add new HTTP client based script template
- When creating a script, you can choose between the old and the new HTTP client based template.
(You have to remove${NGRINDER_HOME}/script_template
directory to apply new script templates)
- When creating a script, you can choose between the old and the new HTTP client based template.
- Use OSSRH when release to maven central
- Change agent configurations
agent.region
has been removed,agent.subregion
andagent.owner
have been added.- See Agent Configuration Guide
- Support controller subregion
- Bug fix
- #788 Fix fail of auto-upgrade from 3.4.x to 3.5.x
ngrinder-3.5.4
- Changes
- Release new experimental HttpClient based on apache httpcomponents-core
- Support modern HTTP specification
- Provide easy-to-use APIs
- See new nGrinder HTTP client guide
- Use controller DNS instead of IP to support agent-controller reconnection in cloud env
- Support script template customization
- Each ngrinder admin can deploy customized script template under ${NGRINDER_HOME}/script_template
- Provide the connection reset option in test configuration page
- If you turn it on, it tries to reuse connection as much as possible.
- Bump Jython standard up to 2.7.2
- Bump internal used Junit up to 4.13.1
- nGrinder no longer depends on specific version of junit for performance test
- Release new experimental HttpClient based on apache httpcomponents-core
- Notice
- If you have a trouble with updating controller from ngrinder 3.4.X to a newer version. Please refer to How to update ngrinder controller
- Bug fix
- #706 Cancel progressing state test when starting controller
- #714 Fix validation error when using AppClassLoader in over JDK9
- #716 Fix script validation error in windows
- #731 Fix not working remember-me
- #739 Fix easy clustering
- #745 Make compatibility with IE11
- #748 Make grinder utils work on Jython performance test
- #773 Fix cannot search user with two characters
- #774, #779 Fix duplicated running test on one user
ngrinder-3.5.3
- Changes
- Support gradle groovy script
- Maven groovy script is deprecated and can't create any more but, it can still run
- Use maven central repository to manage submodules
- Use maven central repository instead of github repository
- Support UTC
- Use linux timestamp instead of string format of date time.
- Support gradle groovy script
- Trivial Fix
- Make several UI improvements
- Add identity information to perftest related log
- Make the H2 console optionally available
- Clean up code
- Bug fix
ngrinder-3.5.2
- Changes
- Support LDAP login
- From now on you can use LDAP for user authentication.
- See LDAP guide
- Support webhook
- When the specified events happen, we'll send a webhook request depends on your configuration.
- See webhook guide
- Support LDAP login
- Trivial Fix
- Make several UI improvements.