jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From benbenw <...@git.apache.org>
Subject [GitHub] jmeter pull request: Bug 56554 : the script cache key is now autom...
Date Thu, 07 Jan 2016 08:54:49 GMT
GitHub user benbenw opened a pull request:

    https://github.com/apache/jmeter/pull/67

    Bug 56554 : the script cache key is now automatically generated.

    The md5 of the script content is used.
    The previous cacheKey property is still there for compatibility but can
    not be modified or viewed in the gui.
    Note that with this change, a Compilable script will always be cached,
    it was not the case with the previous version if the user set the
    cacheKey property to an empty value.
    Documentation *was not* updated.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/benbenw/jmeter jsr223cache

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/jmeter/pull/67.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #67
    
----
commit 4e1c75e83475e1344cb510af6b7bb3b9dd9dd83a
Author: benoit <b.wiart@ubik-ingenierie.com>
Date:   2016-01-07T08:52:15Z

    Bug 56554 : the script cache key is now automatically generated.
    The md5 of the script content is used.
    The previous cacheKey property is still there for compatibility but can
    not be modified or viewed in the gui.
    Note that with this change, a Compilable script will always be cached,
    it was not the case with the previous version if the user set the
    cacheKey property to an empty value.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message