Google Cloud 无法部署应用程序并显示消息“未找到可部署的工件。无法继续。”答案

【问题标题】：Google Cloud fails to deploy app with message "No deployable artifacts were found. Unable to proceed."Google Cloud 无法部署应用程序并显示消息“未找到可部署的工件。无法继续。”
【发布时间】：2021-10-31 09:47:25
【问题描述】：

我正在尝试将基于 Java 的 Web 应用程序部署到 Google Cloud，并且当我使用 gcloud CLI 命令gcloud app deploy 时，正如文档所示，我收到错误消息。这是错误日志的相关部分：

Step #0: Pulling image: gcr.io/gcp-runtimes/java/runtime-builder@sha256:29e14b9a764601f35d88b40fdbf1d2191c2df773d4e788575a3663fa2537bbb1
Step #0: gcr.io/gcp-runtimes/java/runtime-builder@sha256:29e14b9a764601f35d88b40fdbf1d2191c2df773d4e788575a3663fa2537bbb1: Pulling from gcp-runtimes/java/runtime-builder
Step #0: Digest: sha256:29e14b9a764601f35d88b40fdbf1d2191c2df773d4e788575a3663fa2537bbb1
Step #0: Status: Downloaded newer image for gcr.io/gcp-runtimes/java/runtime-builder@sha256:29e14b9a764601f35d88b40fdbf1d2191c2df773d4e788575a3663fa2537bbb1
Step #0: gcr.io/gcp-runtimes/java/runtime-builder@sha256:29e14b9a764601f35d88b40fdbf1d2191c2df773d4e788575a3663fa2537bbb1
Step #0: Exception in thread "main" com.google.cloud.runtimes.builder.exception.ArtifactNotFoundException: No deployable artifacts were found. Unable to proceed.
Step #0:    at com.google.cloud.runtimes.builder.buildsteps.PrebuiltRuntimeImageBuildStep.getArtifact(PrebuiltRuntimeImageBuildStep.java:77)
Step #0:    at com.google.cloud.runtimes.builder.buildsteps.RuntimeImageBuildStep.run(RuntimeImageBuildStep.java:50)
Step #0:    at com.google.cloud.runtimes.builder.BuildPipelineConfigurator.generateDockerResources(BuildPipelineConfigurator.java:104)
Step #0:    at com.google.cloud.runtimes.builder.Application.main(Application.java:147)
Finished Step #0
ERROR
ERROR: build step 0 "gcr.io/gcp-runtimes/java/runtime-builder@sha256:29e14b9a764601f35d88b40fdbf1d2191c2df773d4e788575a3663fa2537bbb1" failed: step exited with non-zero status: 1

我认为关键部分在异常堆栈跟踪中：Exception in thread "main" com.google.cloud.runtimes.builder.exception.ArtifactNotFoundException: No deployable artifacts were found. Unable to proceed.。没有进一步的解释，我找不到关于为什么会发生这种情况的文档。我怀疑这可能与我的构建有关。 mvn clean package 命令确实会在target 目录中生成 jar 文件。下面是我的pom.xml 和app.yaml。如果需要其他信息，请告诉我。由于这个问题对我来说太陌生了，我想不出还需要什么。

pom.xml

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <parent>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-parent</artifactId>
        <version>2.4.0</version>
        <relativePath/> <!-- lookup parent from repository -->
    </parent>
    <groupId>com.example</groupId>
    <artifactId>chess</artifactId>
    <version>0.0.1-SNAPSHOT</version>
    <packaging>jar</packaging>
    <name>chess</name>
    <description>Lite chess UI using Spring Boot</description>

    <properties>
        <java.version>11</java.version>
    </properties>

    <dependencies>

        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-devtools</artifactId>
            <scope>runtime</scope>
            <optional>true</optional>
        </dependency>
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-thymeleaf</artifactId>
        </dependency>
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-web</artifactId>
        </dependency>
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-websocket</artifactId>
        </dependency>
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-json</artifactId>
        </dependency>
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-data-jpa</artifactId>
        </dependency>
<!--        <dependency>-->
<!--            <groupId>org.springframework.boot</groupId>-->
<!--            <artifactId>spring-boot-actuator-autoconfigure</artifactId>-->
<!--        </dependency>-->
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-security</artifactId>
        </dependency>
        <dependency>
            <groupId>org.springframework.security</groupId>
            <artifactId>spring-security-messaging</artifactId>
        </dependency>

        <dependency>
            <groupId>org.thymeleaf.extras</groupId>
            <artifactId>thymeleaf-extras-springsecurity5</artifactId>
            <version>3.0.4.RELEASE</version>
        </dependency>


        <dependency>
            <groupId>com.mchange</groupId>
            <artifactId>c3p0</artifactId>
            <version>0.9.5.5</version>
        </dependency>

        <dependency>
            <groupId>mysql</groupId>
            <artifactId>mysql-connector-java</artifactId>
            <scope>runtime</scope>
        </dependency>

        <dependency>
            <groupId>com.h2database</groupId>
            <artifactId>h2</artifactId>
            <version>1.4.200</version>
            <scope>runtime</scope>
        </dependency>
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-tomcat</artifactId>
            <scope>provided</scope>
        </dependency>
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-test</artifactId>
            <scope>test</scope>
        </dependency>
    </dependencies>

    <build>
        <plugins>
            <plugin>
                <groupId>org.springframework.boot</groupId>
                <artifactId>spring-boot-maven-plugin</artifactId>
            </plugin>

            <plugin>
        <groupId>com.google.cloud.tools</groupId>
        <artifactId>appengine-maven-plugin</artifactId>
        <version>2.4.1</version>
      </plugin>

      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-dependency-plugin</artifactId>
        <version>3.2.0</version>
        <executions>
          <execution>
            <id>copy</id>
            <phase>prepare-package</phase>
            <goals>
              <goal>copy-dependencies</goal>
            </goals>
            <configuration>
              <outputDirectory>
                ${project.build.directory}/appengine-staging
              </outputDirectory>
            </configuration>
          </execution>
        </executions>
      </plugin>

        </plugins>
    </build>

</project>

app.yaml

runtime: java
env: flex

注意：关于env: standard，我收到有关不支持 Java 6 的错误。去搞清楚。我只是在玩弄配置，看看它是否会改变任何东西。

【问题讨论】：

在部署您的应用程序时，您能否尝试使用mvn clean package appengine:deploy 而不是gcloud app deploy？
我试过了。我收到此错误：appengine:run is only available for appengine-web.xml based projects, the service defined in: /home/<name>/ChessLive/target/chess-0.0.1-SNAPSHOT cannot be run by the dev appserver.。使用gcloud deploy 和appengine:run 有什么区别？
我发布了我的答案。

标签： java maven google-app-engine gcloud

【解决方案1】：

根据您要使用的pox.xml java11 运行时：

<properties>
    <java.version>11</java.version>
</properties>

App Engine 灵活

到目前为止，App Engine Flexible 不支持java11 运行时，但可以使用custom runtime 和Dockerfile 来实现。您可以使用此示例setup 作为参考来拥有这种运行时环境。

App Engine 标准

通过在app.yaml 中声明java11 在App Engine Standard 中支持java11 运行时，例如：

app.yaml

runtime: java11

应用部署

如果您正在使用 Maven 插件，您应该使用 mvn clean package appengine:deploy 命令，以便在 App Engine 中正确 deploy your application 并避免此类错误：

线程“主”com.google.cloud.runtimes.builder.exception.ArtifactNotFoundException 中的异常：未找到可部署的工件。无法继续。

gcloud app deploy 和mvn appengine:deploy 的区别在于gcloud app deploy 是使用gcloud 工具在App Engine 中部署您的应用程序的命令，而mvn appengine:deploy 使用的是Maven 插件。

【讨论】：

如果您对我的回答有任何澄清或疑问，请告诉我。如果您认为我的回答中的信息有帮助，您可以接受或投票。