如何使用私有文件配置 TeamCity?

发布于 2024-11-24 08:48:59 字数 452 浏览 2 评论 0 原文

我正在设置 TeamCity 进行持续集成和(希望如此)持续部署。一些构建步骤将涉及私有文件,例如

  • 用于强命名的 .snk 文件 .NET 程序集
  • 用于发布工件的密码/令牌文件(例如 NuGet 或 CodePlex)

由于这些文件包含私有数据,我不想将它们放入(可公开访问的)源代码控制系统。

我正在为 http://teamcity.codebetter.com .codeplex.com/" rel="noreferrer">AutoFixture 所以我没有对服务器的物理访问权限。我希望有一个功能可以让我上传此类文件,但找不到任何此类文件。

最合适的解决方案是什么?

I'm setting up TeamCity for Continuous Integration and (hopefully) Continuous Deployment. Some of the build steps will involve private files, e.g.

  • .snk files for strong naming .NET assemblies
  • password/token files for publishing artifacts (for example to NuGet or CodePlex)

Since these files contain private data I don't want to put them into the (publicly accessible) source control system.

I'm setting up http://teamcity.codebetter.com for AutoFixture so I don't have physical access to the server. I was hoping for a feature that would let me upload such files, but can't find anything of the kind.

What would be the most appropriate solution?

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

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

发布评论

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

评论(2

雪落纷纷 2024-12-01 08:48:59

TeamCity 支持多个 VCS 根目录,因此您只需添加一个带有这些私有文件的额外 VCS 根目录即可。

显然,这需要第二个存储库是私有的 - 但这正是您想要的。将这些文件置于源代码管理中是一件很棒的事情。

TeamCity supports multiple VCS roots, so you could just add an extra VCS root with these private files.

Obviously this would require that the second repository is private - but that is what you want any way. Having those files in source control is a great thing.

戒ㄋ 2024-12-01 08:48:59

我会将所需的文件放入源代码管理中,但我会首先对它们进行加密。然后,我会在构建中设置一个参数,该参数是解密文件所需的密码或密钥。构建将解密文件,执行所需的任何签名或发布,然后删除它们(如果系统允许,则擦除它们)。这应该足以保证一切安全,除非团队城市受到损害,如果是的话,你基本上就沉没了。

根据您使用的源代码管理工具,可以将文件设置为仅对某些经过身份验证的用户可见。 Perforce 当然具有此功能,但我从未见过更流行的 DVCS 系统的任何功能。

I would put the files I needed in source control but I would first encrypt them. I would then set up a parameter in the build which was the passphrase or key required to decrypt the files. The build would decrypt the files do whatever signing or publishing was needed with them and then delete them (wipe them if the system allows for such). This should be enough to keep things safe unless team city is compromised and if it is you're basically sunk anyway.

Depending on the source control tools you use it might be possible to set the files to only be visible by certain authenticated users. Perforce certainly has this capability but I've never seen anything for the more popular DVCS systems.

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