如何通过Gradle任务运行JMeter GUI？

Question

我想从我的Gradle脚本运行JMeter GUI，这样我就可以仔细控制版本和环境因素，这样我的本地开发人员机器构建¹就没有必要的设置了。

我的JMeter的构建。gradle（多项目构建的一部分）：

plugins{
  id 'base'
  id 'java'
}

repositories {
  jcenter()
}

dependencies {
  compile 'org.apache.jmeter:ApacheJMeter:4.0'
}

task jmeterGui(type: JavaExec){
  workingDir = "$project.buildDir/jmeter-working-dir"
  classpath = sourceSets.main.runtimeClasspath

  main = "org.apache.jmeter.NewDriver"

  doFirst{
    println "running Jmeter from Gradle"
    mkdir workingDir

  }
}

> Task :functional-test:jmeterGui
java.lang.Throwable: Could not access <source root>\functional-test\build\lib
  at org.apache.jmeter.NewDriver.<clinit>(NewDriver.java:102)
java.lang.Throwable: Could not access <source root>\functional-test\build\lib\ext
  at org.apache.jmeter.NewDriver.<clinit>(NewDriver.java:102)
java.lang.Throwable: Could not access <source root>\functional-test\build\lib\junit
  at org.apache.jmeter.NewDriver.<clinit>(NewDriver.java:102)
java.lang.ClassNotFoundException: org.apache.jmeter.JMeter
  at java.net.URLClassLoader$1.run(URLClassLoader.java:372)
  at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
  at java.security.AccessController.doPrivileged(Native Method)
  at java.net.URLClassLoader.findClass(URLClassLoader.java:360)
  at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
  at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
  at org.apache.jmeter.NewDriver.main(NewDriver.java:242)
JMeter home directory was detected as: <source root>\functional-test\build

¹目前，在我的构建中，所有内容都受到严格的版本控制，是Gradle构建的一部分。这包括NodeJS、NPM和Terraform。从字面上看，唯一的设置先决条件是Java8 JDK。我想用JMeter继续这种方法。

Answer 1

下面是我目前从Gradle运行JMeter GUI的最佳尝试。注意，GUI启动了，但是几乎不起作用（甚至不能打开测试计划）。

dependencies {
  // using the runtime classpath instead of compile in order to avoid
  // downloading all these and their deps in places where we never intend
  // to run the JMeter GUI (continuous build environments, etc.)
  runtime 'org.apache.jmeter:ApacheJMeter:4.0'
  runtime 'org.apache.jmeter:jorphan:4.0'
  runtime 'org.apache.jmeter:ApacheJMeter_core:4.0'
  runtime 'org.apache.jmeter:ApacheJMeter_components:4.0'
  runtime 'org.apache.jmeter:ApacheJMeter_config:4.0'
  runtime 'org.apache.jmeter:ApacheJMeter_functions:4.0'
  runtime 'org.apache.jmeter:ApacheJMeter_java:4.0'
  runtime 'org.apache.jmeter:ApacheJMeter_http:4.0'
  runtime 'org.apache.jmeter:ApacheJMeter_tcp:4.0'
  runtime 'org.apache.jmeter:ApacheJMeter_parent:4.0'
}

task launchJmeterGui(type: JavaExec){
  description = "Launch the JMeter GUI for editin test plans"
  workingDir = "$project.buildDir/jmeter-working-dir"
  classpath = sourceSets.main.runtimeClasspath

  // This is the main class that the jmeter.bat file invokes.
  // I think this thing is specifically intended to be invoked from a batch/
  // shell script and is not intended to be invoked like this.
  main = "org.apache.jmeter.NewDriver"

  // I think this controls where the log file goes, not sure.
  args "--homedir=${workingDir.absolutePath}"

  doFirst{
    println "Launching Jmeter from Gradle"

    // log file ends up in here
    mkdir workingDir

    // I don't put anything in here, but there will be errors in the console
    // output if they don't exist.  I think this is where the darcula jar
    // needs to be in order to work?
    mkdir "$buildDir/lib"
    mkdir "$buildDir/lib/ext"
    mkdir "$buildDir/lib/junit"

    // Copied into the source tree from a JMeter 4.0 install.
    // Will run without these files but will print errors to console/log file.
    // I'm happy to put these under source control, that makes sense to me.
    project.copy {
      from "src/test/resources/jmeter.properties"
      from "src/test/resources/log4j2.xml"
      into "$buildDir/bin"
    }

  }
}