Aws Code 管道在部署阶段因超时而失败 [英] Aws Code pipeline is failing at Deployment stage by timing out

本文介绍了Aws Code 管道在部署阶段因超时而失败的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在努力为应用程序的 Api 部分提供 ci/cd.

I am trying to work my way to have a ci/cd for the Api part of the application.

我有 3 个步骤:

1:来源(git hub version2)

1: Source (git hub version2)

2:构建(目前没有命令)

2: Build (currently has no commands)

3:部署(提供者是代码部署(应用程序))

3: Deploy(provider is code deploy(application))

这是代码部署中的事件截图.

Here is the screenshot of the events in code deploy.

.

在创建部署组时.我选择了从选项中下载代码部署提供程序的选项(尽管这是必要的).

While creating the Deployment Group. I chose the option of downloading the code deploy provider from the option(though it was necessary).

在设置代码管道时选择

觉得合适.

此代码管道已将一个对象放入此管道的 S3 存储桶中.代码部署正在对该源工件起作用.

This code pipeline has put an object into the S3 bucket for this pipeline. Code deploy is acting on that source artifact.

注意:我们在这个 Ec2 映像上什么都没有,它只是我们拥有 API 的地方.目前,Ec2 为空.

Note: We have nothing on this Ec2 image it's just a place where we have our API. Currently, Ec2 is empty.

实现这一点的正确方法是什么?我该如何克服我所面临的问题.

What would be the proper way to implement this? How can I overcome the issues I am facing.

推荐答案

如果没有 appspec.yml,您的部署将失败.来自 docs:

Without appspec.yml your deployment will fail. From docs:

AppSpec 文件必须是一个名为 appspec.yml 的 YAML 格式文件,并且它必须放在应用程序源代码目录结构的根目录中.否则,部署失败.

An AppSpec file must be a YAML-formatted file named appspec.yml and it must be placed in the root of the directory structure of an application's source code. Otherwise, deployments fail.

这篇关于Aws Code 管道在部署阶段因超时而失败的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆