通过Jenkins Pipeline调用 MeterSphere的测试计划失败

MeterSphere 版本:v2.10.6-lts-e87e920c
jenkins-plugin版本:metersphere-jenkins-plugin-v2.10.6-lts.hpi
运行方式(安装包运行)

通过Jenkins Pipeline调用 MeterSphere的测试计划失败

jenkins的脚本

以下是Jenkins的报错日志:

:36:23.094+0000 [id=1055]  INFO    o.c.j.p.k.KubernetesLauncher#launch: Pod is running: kubernetes kube-ops/jnlp-kaniko-2p732
2023-09-19 06:36:31.280+0000 [id=1009]  SEVERE  i.m.commons.utils.LogUtil#error: Method[auth][null]
java.lang.NullPointerException
        at io.metersphere.client.MeterSphereClient.aesEncrypt(MeterSphereClient.java:364)
        at io.metersphere.client.MeterSphereClient.auth(MeterSphereClient.java:354)
        at io.metersphere.client.MeterSphereClient.call(MeterSphereClient.java:333)
        at io.metersphere.client.MeterSphereClient.call(MeterSphereClient.java:326)
        at io.metersphere.client.MeterSphereClient.checkLicense(MeterSphereClient.java:375)
        at io.metersphere.MeterSphereBuilder.perform(MeterSphereBuilder.java:93)
        at jenkins.tasks.SimpleBuildStep.perform(SimpleBuildStep.java:123)
        at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:101)
        at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:71)
        at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:829)
2023-09-19 06:36:31.699+0000 [id=1148]  INFO    o.c.j.p.k.KubernetesSlave#_terminate: Terminating Kubernetes instance for agent jnlp-kaniko-2p732
2023-09-19 06:36:31.734+0000 [id=1148]  INFO    o.c.j.p.k.KubernetesSlave#deleteSlavePod: Terminated Kubernetes instance for agent kube-ops/jnlp-kaniko-2p732
2023-09-19 06:36:31.734+0000 [id=1148]  INFO    o.c.j.p.k.KubernetesSlave#_terminate: Disconnected computer jnlp-kaniko-2p732
2023-09-19 06:36:31.736+0000 [id=997]   INFO    j.s.DefaultJnlpSlaveReceiver#channelClosed: Computer.threadPoolForRemoting [#50] for jnlp-kaniko-2p732 terminated: java.nio.channels.ClosedChannelException
2023-09-19 06:36:31.874+0000 [id=1055]  INFO    o.j.p.workflow.job.WorkflowRun#finish: Ms-Pipeline-test #39 completed: FAILURE

jenkins有个自动生成pipeline脚本的功能,建议使用自动生成调用MeterSphere的脚本,跟你这个对比下。

片段生成器。

生成的脚本没有问题,请问题可以如何排查呢?

对比下生成的脚本跟你写的有什么区别,直接把生成的脚本,放到你的pipeline里使用也可以。

对比了生成脚本没有问题,下面就是生成脚本,就是没有调起测试计划,请问题如何排查问题呢?
同个Jenkins任务中,添加了执行方式:测试计划和测试用例
测试计划执行不通过
测试用例可以执行通守

是不是平台那边测试计划还在执行中,然后jenkins又调用了?如果执行中,不可以再次调用的