AWS Codepipeline是否将工件中的符号链接传递给Codebuild [英] Will AWS Codepipeline pass symlinks to Codebuild in artifacts

问题描述

我的github存储库中有一些符号链接.

I have some symlinks in my github repo.

当我有一个直接从github克隆的Codebuild项目时，将保留符号链接.

When I have a Codebuild project that clones directly from github, symlinks are preserved.

我进行了切换，以便Codepipeline监听我在github中的dev分支中的更改，并将工件传递给codebuild.

I switched so that Codepipeline listens for changes in my dev branch in github, and passes the artifacts to codebuild.

自从进行此切换以来，Codebuild不再能看到符号链接.

Since making this switch, Codebuild can't see the symlinks anymore.

这是设计使然，还是我的代码管道配置方式中缺少某些东西?

Is this by design, or am I perhaps missing something in how my codepipeline is configured?

推荐答案

到目前为止，AWS CodePipeline不支持源代码中的符号链接.请参阅源工件无法正确处理符号链接或文件模式，讨论论坛，我们可以看到

Up to now, AWS CodePipeline doesn't support symlinks in source. Refer to Source artifact doesn't properly handle symlinks or file modes in discussion forums, we can see

我们已经有了一个带有初始源"的管道设置.阶段来自GitHub上的私人仓库.回购内容被压缩，并最终成为管道的第一个输入工件.

We've got a pipeline setup with an initial "Source" stage coming from a private repo on GitHub. The repo contents get zipped up and end up as the first input artifact for the pipeline.

我注意到zip工件存在一些问题:

I've noticed a couple of issues with the zip artifact:

1.)符号链接不是作为正确的符号链接通过的，而是文本文件，其内容是符号链接指向的位置.

1.) Symlinks don't come through as proper symlinks but rather text files with the content being the location that the symlink points to.

也许AWS CodePipeline团队会在将来对其进行修复.

Maybe AWS CodePipeline team will fix it in the future.

这篇关于AWS Codepipeline是否将工件中的符号链接传递给Codebuild的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！