AWS Codepipeline资产

发布于 2025-02-07 09:48:30 字数 224 浏览 3 评论 0原文

在AWS CodePipeline中,每个管道都带有“阶段” source构建updatePipelineAssets,通过框架。

在这种情况下,该阶段称为Assets的目的到底是什么?

这些文件集的内容是否仅与当前管道执行相关,或者与后续管道执行有关?

In AWS CodePipeline every pipeline comes with the "stages" Source, Build, UpdatePipeline and Assets, which are provided by the framework.

What exactly is the purpose of the stage called Assets in this case?

Are contents of these file sets referenced in the Assets stage relevant for the current pipeline execution only, or are they relevant for subsequent pipeline executions, too?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

情绪操控生活 2025-02-14 09:48:30

您能指出我概述这些阶段的URL吗?与Codepipeline合作已有两年了,亚马逊支持的阶段如下:

以下是CodePipeline中的有效操作类别:

  1. 构建
  2. 测试
  3. exploy sest
  4. experion
  5. deploy批准

可能发生的事情,我必须只是猜测,那就是有人将您的阶段命名为您的阶段。我们需要查看buildspec来告诉您他们的工作。如果您可以分享,我们还可以提供更好的指导,还可以提供指向您所引用的阶段的参考链接。

Can you point me to the URL that outlines those stages? Been working with Codepipeline for two years and the stages supported by Amazon are as follows:

The following are the valid action categories in CodePipeline:

  1. Source
  2. Build
  3. Test
  4. Deploy
  5. Approval
  6. Invoke

URL Reference

What might be happening and i must just speculating, is that someone named your stages a specific name for the pipeline. We need to see the buildspec to tell you what they do. If you can share that we can provide better guidance also the reference links to those stages you are referring to.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文