为什么 Hudson 无法访问我的“srcsafe.ini”？文件？
我正在尝试配置 Hudson VSS 插件来访问特定的 Sourcesafe 存储库以检索文件并进行轮询。
我知道我已经在插件的字段上配置了正确的信息，但我仍然遇到访问错误。
任何人都可以就我的设置可能存在的问题提出建议吗？ （我已经尽可能多地排除故障了..）
I'm trying to configure the Hudson VSS Plugin to access a particular Sourcesafe repository to retrieve files and for polling.
I know I've got the proper information configured on the fields for the plugin, but I'm still getting access errors.
Can anyone offer suggestions as to what might be the problem with my setup? (I've already done as much trouble-shooting as I can..)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我能够通过将 Hudson 配置为在指定用户帐户而不是本地系统帐户下运行来解决访问问题。
实际上，我这样做的目的是将我的 SourceSafe 共享映射为驱动器，然后在 VSS 插件配置中使用该信息（为此我需要指定用户，因为映射的驱动器不在用户之间共享，并且不可用于本地系统帐户），但是一旦我开始在指定帐户下运行 Hudson 服务，我就可以毫无问题地访问我的 srcsafe.ini 文件。
注意：您还需要通过文件夹属性上的“安全”选项卡授予指定用户帐户对 Hudson/Jenkins 目录的访问权限。对于我的构建，我还必须根据我正在编译的内容授予对“临时 ASP.NET 文件”文件夹的访问权限。
I was able to resolve my access issues by configuring Hudson to run under a named user account rather than the Local System Account.
I had actually done this with the intention of mapping my SourceSafe share as a drive and then using that information in the VSS plugin configuration (I needed a named user for this since mapped drives aren't shared between users and are not available to the Local System Account), but once I started running the Hudson service under the named account, I was able to access my srcsafe.ini file without any issues.
NOTE: You'll also want to grant the named user account access to the Hudson/Jenkins directory via the Security tab on the folder properties. For my builds, I also had to give access to the 'Temporary ASP.NET Files' folder based on what I was compiling.