jmeter-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 60886] New: Document building and testing in corporate environments
Date Fri, 17 Mar 2017 20:59:07 GMT

            Bug ID: 60886
           Summary: Document building and testing in corporate
           Product: JMeter
           Version: 3.1
          Hardware: All
                OS: All
            Status: NEW
          Severity: major
          Priority: P2
         Component: Main
  Target Milestone: ---

Building and testing JMeter in a corporate environment is hard if your are
locked down and have outbound access via HTTP proxy only. See bug 60883.

1. Building: build.xml requires direct, outbound access to the Internet. You
can fiddle around it by applying following patch:
> diff --git a/build.xml b/build.xml
> index 4ddd4513f..08c2fdf83 100644
> --- a/build.xml
> +++ b/build.xml
> @@ -3052,7 +3052,8 @@ run JMeter unless all the JMeter jars are added.
>    <!-- Download a jar file and check its hash; if correct, move to correct directory
>    <target name="_get_jarfile" if="_get_jarfile" unless="file.exists">
>      <echo message="Fetching: ${path}/${jar}" level="info"/>
> -    <get src="${loc}/${jar}"
> +    <setproxy proxyhost="${}" proxyport="${proxy.port}"/>
> +       <get src="${loc}/${jar}"
>           dest="${build.dir}/${jar}"
>           usetimestamp="false" ignoreerrors="false"/>
>      <antcall target="_checkMD5">
Values are in Username/password for proxy can be
supplied optionally.
2. Testing: several tests require hard outbound connection to (DNS) or
proxy sampler test to Impossible to pass tests.

Document both issues in and building.html.

People should be aware that this is problematic before wasting time to figure
out what's wrong.

You are receiving this mail because:
You are the assignee for the bug.
View raw message