Question

我正在尝试使用cobertura插件生成代码覆盖率报告。

我在pom.xml中有这种依赖

<plugin>
     <groupId>org.codehaus.mojo</groupId>
     <artifactId>cobertura-maven-plugin</artifactId>
     <version>2.6</version>
     <executions>
         <execution>
             <phase>test</phase>
             <goals>
              <goal>cobertura</goal>
             </goals>
             <configuration>
                 <formats>
                     <format>html</format>
                     <format>xml</format>
                  </formats>
             </configuration>
         </execution>
     </executions>
  <configuration>
      <formats>
          <format>html</format>
          <format>xml</format>
    </formats>
</configuration>

当我使用这个目标构建我的项目-U -B clean install cobertura：cobertura时，我在jenkins CI上得到以下错误

 16:37:31 [ERROR] Failed to execute goal org.codehaus.mojo:cobertura-maven-plugin:2.6:instrument (default-cli) on project TestModule: Unable to execute Cobertura. Error while executing process. Cannot run program "/bin/sh": error=7, Argument list too long -> [Help 1]
16:37:31 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:cobertura-maven-plugin:2.6:instrument (default-cli) on project TestModule: Unable to execute Cobertura.
16:37:31    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
16:37:31    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
16:37:31    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
16:37:31    at org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions(MojoExecutor.java:364)
16:37:31    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:198)
16:37:31    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
16:37:31    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
16:37:31    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
16:37:31    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
16:37:31    at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
16:37:31    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
16:37:31    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
16:37:31    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
16:37:31    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
16:37:31    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
16:37:31    at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
16:37:31    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
16:37:31    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:76)
16:37:31    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
16:37:31    at java.lang.reflect.Method.invoke(Method.java:602)
16:37:31    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
16:37:31    at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
16:37:31    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
16:37:31    at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
16:37:31 Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to execute Cobertura.
16:37:31    at org.codehaus.mojo.cobertura.tasks.AbstractTask.executeJava(AbstractTask.java:244)
16:37:31    at org.codehaus.mojo.cobertura.tasks.InstrumentTask.execute(InstrumentTask.java:139)
16:37:31    at org.codehaus.mojo.cobertura.CoberturaInstrumentMojo.execute(CoberturaInstrumentMojo.java:162)
16:37:31    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)
16:37:31    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
16:37:31    ... 23 more
16:37:31 Caused by: org.codehaus.plexus.util.cli.CommandLineException: Error while executing process.
16:37:31    at org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java:656)
16:37:31    at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:144)
16:37:31    at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:107)
16:37:31    at org.codehaus.mojo.cobertura.tasks.AbstractTask.executeJava(AbstractTask.java:240)
16:37:31    ... 27 more
16:37:31 Caused by: java.io.IOException: Cannot run program "/bin/sh": error=7, Argument list too long
16:37:31    at java.lang.ProcessBuilder.start(ProcessBuilder.java:1042)
16:37:31    at java.lang.Runtime.exec(Runtime.java:615)
16:37:31    at java.lang.Runtime.exec(Runtime.java:526)
16:37:31    at org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java:636)
16:37:31    ... 30 more
16:37:31 Caused by: java.io.IOException: error=7, Argument list too long
16:37:31    at java.lang.UNIXProcess.<init>(UNIXProcess.java:139)
16:37:31    at java.lang.ProcessImpl.start(ProcessImpl.java:152)
16:37:31    at java.lang.ProcessBuilder.start(ProcessBuilder.java:1023)
16:37:31    ... 33 more

我的Windows机器上的构建成功但jenkins 失败。当我将cobertura版本降级到2.5.1时，这个错误就消失了，但我得到了一些解析异常，因为cobertura for 2.5.1的解析器与java语法不是最新的。

有人可以帮助我让这个适用于2.6.0版及更高版本的cobertura

Answer 1

这与相关方面有关，但可能会提供帮助

这是由linux限制引起的，其中参数的大小不能超过128kb 请参阅Linux内核常量：MAX_ARG_STRLEN https://github.com/torvalds/linux/blob/master/include/uapi/linux/binfmts.h

在Jenkins中，一旦您读取/超出了超出此值的变量，您将遇到此错误。在我的例子中，我有一个github webhook，它启动了Jenkins作业并将有效负载参数设置为某个字符串＆gt;比这个限制。尝试读取此参数会引发此错误。

为了解决这个问题，我有一个使用rest-api调用来读取父级值的子作业

您可以让父作业失败，但允许在所有情况下启动子作业。下面是一个稍微改进的函数，我用它来提取信息（为了简洁而删除了错误检查和注释）

def get_parameter_value_from_parent():
    host = 'https://[YOUR_COMPANY].ci.cloudbees.com'
    this_build_url = os.environ.get('BUILD_URL')
    request_auth = (JENKINS_USER, JENKINS_TOKEN)

    url = '{0}/api/json'.format(this_build_url)
    parameter_name = 'payload'
    payload = ''

    #
    # Get the upstreamBuild number, and the upstreamUrl
    # so we can put together a link to the upstream job
    #

    response = requests.get(url, auth=request_auth)
    this_build = json.loads(response)

    build_number = ''
    short_url = ''
    actions = this_build['actions']
    for action in actions:
        if action.get('causes'):
            for cause in action.get('causes'):
                build_number = cause['upstreamBuild']
                short_url = cause['upstreamUrl']

    parent_url = '{host}/{short_url}{build}/api/json'.format(host=host,
            short_url=short_url, build=build_number)

    #
    # Now get the payload from the parent job by making REST api call
    #

    response = requests.get(parent_url, auth=request_auth)
    upstream_build = json.loads(response)

    actions = upstream_build['actions']
    for action in actions:
        if action.get('parameters'):
            for parameter in action.get('parameters'):
                if parameter['name'] == parameter_name:
                    value = parameter['value']
                    payload = value
                    return payload

    print 'Error: Unable to return payload from parent jenkins job: {0}'.format(parent_url)
    sys.exit(1)

Answer 2

所有shell都有命令行长度的限制。 UNIX / Linux / BSD系统对命令行参数和环境变量可以使用的字节数有限制。

当您启动新进程或键入命令时会应用这些限制，您将在屏幕上看到如下错误消息：

Argument list too long

Cobertura正在尝试执行shell命令：

getLog().debug( "Working Directory: " + cl.getWorkingDirectory() );
getLog().debug( "Executing command line:" );
getLog().debug( cl.toString() );

int exitCode;
try
{
    exitCode = CommandLineUtils.executeCommandLine( cl, stdout, stderr );
}
catch ( CommandLineException e )
{
    throw new MojoExecutionException( "Unable to execute Cobertura.", e );
}

事实上，该插件正在尝试执行一个java进程来运行cobertura：

 Commandline cl = new Commandline();
 File java = new File( SystemUtils.getJavaHome(), "bin/java" );
 cl.setExecutable( java.getAbsolutePath() );
 cl.addEnvironment("CLASSPATH", createClasspath());

 String log4jConfig = getLog4jConfigFile();
 if ( log4jConfig != null )
 {
     cl.createArg().setValue( "-Dlog4j.configuration=" + log4jConfig );
 }

 cl.createArg().setValue( "-Xmx" + maxmem );

 cl.createArg().setValue( taskClass );

 if ( cmdLineArgs.useCommandsFile() )
 {
     String commandsFile;
     try
     {
          commandsFile = cmdLineArgs.getCommandsFile();
     }
     catch ( IOException e )
     {
           throw new MojoExecutionException( "Unable to obtain CommandsFile location.", e );
     }
     if ( FileUtils.fileExists( commandsFile ) ) 
     {
            cl.createArg().setValue( "--commandsfile" );
            cl.createArg().setValue( commandsFile );
      }
      else 
      {
             throw new MojoExecutionException( "CommandsFile doesn't exist: "  + commandsFile );
      }
 }
 else
 {
      Iterator<String> it = cmdLineArgs.iterator();
      while ( it.hasNext() )
      {
          cl.createArg().setValue( it.next() );
      }
 }

因此，首先，启用cobertura DEBUG跟踪以显示已执行的shell命令。

我认为问题是版本2.6中使用的类路径与版本2.5.1中使用的类路径。

请启用调试跟踪并发布结果：

https://wiki.jenkins-ci.org/display/JENKINS/Logging

Cobertura给出的参数列表太长了

2 个答案: