JHipster Jenkins构建失败

克里斯多夫

我必须解决现有JHipster项目上的构建问题。几天前情况还不错,所以我不知道发生了什么。基本上,这是JHipster中针对3种微服务的Jenkins构建。构建依赖于docker映像并使用maven包装器mvnw。这是jenkinsfile的摘录:

        parallel 'Gateway': {
            dir('jh-ambient-gateway') {

                docker.image('registry.hub.docker.com/circleci/openjdk:11.0-jdk-stretch-node-browsers').inside("--group-add ${dockerGroup} -v /var/run/docker.sock:/var/run/docker.sock") {

                    stage('check java') {
                        sh "java -version"
                    }

                    stage('clean') {
                        sh "chmod +x mvnw"
                        sh "./mvnw clean"
                    }

                    stage('install tools') {
                        sh "./mvnw com.github.eirslett:frontend-maven-plugin:install-node-and-npm -DnodeVersion=v12.14.1 -DnpmVersion=6.13.0"
                    }

                    stage('npm install') {
                        sh "./mvnw com.github.eirslett:frontend-maven-plugin:npm"
                    }

。\ mvnw clean指令生成失败。我们可以在下面的日志中看到插入了一个名为“ / tmp”的附加目标,该目标对系统而言是未知的。它是反应堆建造计划的一部分。我在我们的项目中搜索了此字符串,但没有找到它的来源。

构建日志:

[DEBUG] Writing tracking file /home/node/.m2/repository/org/springframework/session/spring-session-bom/Bean-SR8/_remote.repositories
[DEBUG] Writing tracking file /home/node/.m2/repository/org/springframework/session/spring-session-bom/Bean-SR8/spring-session-bom-Bean-SR8.pom.lastUpdated
[DEBUG] === REACTOR BUILD PLAN ================================================
[DEBUG] Project: com.xxxx.yyyy:zzzz:jar:0.0.1-SNAPSHOT
[DEBUG] Tasks:   [/tmp, clean]
[DEBUG] Style:   Regular
[DEBUG] =======================================================================
[INFO] 
[INFO] -------------------< com.xxxx.yyyy:zzzz >-------------------
[INFO] Building zzzz 0.0.1-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
[DEBUG] Lifecycle default -> [validate, initialize, generate-sources, process-sources, generate- resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  5.354 s
[INFO] Finished at: 2020-03-31T11:58:55Z
[INFO] ------------------------------------------------------------------------
[ERROR] Unknown lifecycle phase "/tmp". You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1]
org.apache.maven.lifecycle.LifecyclePhaseNotFoundException: Unknown lifecycle phase "/tmp". You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy.
    at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateLifecycleMappings (DefaultLifecycleExecutionPlanCalculator.java:248)
    at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateMojoExecutions (DefaultLifecycleExecutionPlanCalculator.java:217)
    at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan (DefaultLifecycleExecutionPlanCalculator.java:126)
    at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan (DefaultLifecycleExecutionPlanCalculator.java:144)
    at org.apache.maven.lifecycle.internal.builder.BuilderCommon.resolveBuildPlan (BuilderCommon.java:97)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:111)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.apache.maven.wrapper.BootstrapMainStarter.start (BootstrapMainStarter.java:39)
    at org.apache.maven.wrapper.WrapperExecutor.execute (WrapperExecutor.java:122)
    at org.apache.maven.wrapper.MavenWrapperMain.main (MavenWrapperMain.java:61)

我的问题是:

  1. “清洁”目标在哪里定义?我相信这是Maven核心目标的一部分,但是我想确定的是,如果我有机会验证/ tmp在那里没有定义的话。
  2. 这个“ / tmp”目标在哪里定义?如何删除或修复它?
  3. 我应该更改我的Docker映像并拍摄另一个吗?在这种情况下,哪个知道我需要Jdk 11。

谢谢克里斯托夫

克里斯多夫

一位同事找到了解决方案。变量MAVEN_CONFIG设置不正确。

因此需要在jenkinsfile中编写以下代码:

sh“未设置MAVEN_CONFIG && ./mvnw干净”

本文收集自互联网,转载请注明来源。

如有侵权,请联系[email protected] 删除。

编辑于
0

我来说两句

0条评论
登录后参与评论

相关文章

来自分类Dev

JHipster - 纱线构建失败

来自分类Dev

在Windows Jenkins中构建jhipster

来自分类Dev

JHipster postgresql 连接失败

来自分类Dev

Jhipster博客项目登录失败

来自分类Dev

Android Jenkins蚂蚁构建失败

来自分类Dev

Android Jenkins蚂蚁构建失败

来自分类Dev

构建 Jenkins Docker 镜像失败

来自分类Dev

如何使失败的 DotnetCore 构建破坏 Jenkins 构建?

来自分类Dev

CORS Origin Spring Boot Jhipster-飞行前失败

来自分类Dev

由于缺少android SDK,Jenkins构建失败

来自分类Dev

Jenkins使用Gradle守护程序构建失败

来自分类Dev

Jenkins构建因Windows上的GitLockFailedException而失败

来自分类Dev

Jenkins构建因修订错误而失败

来自分类Dev

Jenkins构建在执行Shell时失败

来自分类Dev

Android Jenkins构建因crashlytics失败

来自分类Dev

Jenkins使用工作区构建失败

来自分类Dev

从Jenkins运行Katalon Studio时构建失败

来自分类Dev

Jenkins构建中的未知断言失败

来自分类Dev

Jenkins因轮询失败而触发构建

来自分类Dev

Jenkins Workflow插件如何使构建失败

来自分类Dev

使用最新 jenkins 构建的 RPM 部署失败

来自分类Dev

由于 Maven,简单的 Jenkins 管道构建失败

来自分类Dev

Jenkins 因“PKIX 路径构建”错误而失败

来自分类Dev

即使后期构建脚本失败,Jenkins构建也会成功

来自分类Dev

当我使用 Jenkins 构建时,Android 构建总是失败

来自分类Dev

当Maven单元测试失败时,如何使Jenkins构建失败?

来自分类Dev

定制JHipster

来自分类Dev

如何使用Jhipster,Docker,Gitlab和Heroku进行构建,测试和部署

来自分类Dev

如何使用Jhipster,Docker,Gitlab和Heroku进行构建,测试和部署