blocks|key|2137866|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2137867|+SET+WORKING_COPY=//ip-address/users/myDirB|blockquote|2137868|2137869|2137870|无法工作，因为cmd.exe需要一个简单的路径(驱动器号、冒号、相对路径)。它不能处理其他路径，如UNC或ip地址。它必须有一个驱动器字母。|2137871|2137872|集WORKING_COPY=H:/myDirB|2137873|2137874|2137875|但是，这不起作用，因为您将H:映射到您所登录的用户的某个位置。但是钩子脚本是在运行svn服务器的用户时运行的，即作为服务帐户运行。服务帐户而不是映射了H:驱动器。|offset|length|style|BOLD|CODE|2137876|entityMap^0|0|0|0|0|0|0|0|0|0|1X|3|23|2|0^^$0|@$1|2|3|-4|4|5|6|V|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|W|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|X|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|Y|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|Z|7|@]|8|@]|9|$]]|$1|H|3|-4|4|5|6|10|7|@]|8|@]|9|$]]|$1|I|3|J|4|C|6|11|7|@]|8|@]|9|$]]|$1|K|3|-4|4|5|6|12|7|@]|8|@]|9|$]]|$1|L|3|-4|4|5|6|13|7|@]|8|@]|9|$]]|$1|M|3|N|4|5|6|14|7|@$O|15|P|16|Q|R]|$O|17|P|18|Q|S]]|8|@]|9|$]]|$1|T|3|-4|4|5|6|19|7|@]|8|@]|9|$]]]|U|$]]

<blockquote>
 SET WORKING_COPY=//ip-address/users/myDirB
</blockquote>

can not work, since cmd.exe needs a plain path (drive letter, colon, relative path). It can not deal with other paths like UNC or ip addresses. It must have a drive letter.

<blockquote>
 SET WORKING_COPY=H:/myDirB
</blockquote>

this however doesn't work because you mapped H: to something as the user you're logged on. But the hook script is running as the user your svn server is running, i.e. as the service account. And the service account does not have the <code>H:</code> drive mapped.

blocks|key|2137905|text|我建议不要使用post提交钩子来这样做。它将永远是脆弱的，复杂的--正如你所发现的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2137906|您应该设置一个持续的集成构建，它监视svn回购，然后在需要时部署代码。将这些关注点分开将在将来避免您的头痛，提供通知团队(IM、电子邮件或仪表板)的简单方法，并在/如果希望进行任何自动化测试时帮助您解决问题。|2137907|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I would recommend against using a post commit hook to do this. It's going to be forever brittle, and complicated - as you're finding out.

You should setup a continuous integration build that monitors the svn repo and then deploys the code if needed. Separating these concerns will save you headache in the future, provide easy way to notify team (IM, email or dashboard), and will help you out when/if wish to do any automated testing.

blocks|key|562456|text|我遇到的两个问题是(1)路径和(2)权限。我们以前的设置包括collabnet+subversion服务器1.5.6和Windows2008+R2上的apache2.2+(现在wandisco+1.7.2+/apache2.2在Win+2008+R2上)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|562457|最初，我将路径作为映射驱动器，subversion和apache服务作为本地系统帐户运行。所以，我们有这样的事情：|562458|SET+WORKING_COPY=X:\the\path\to\theworkingcopy|code-block|syntax|javascript|562459|通过CLI运行它是很好的，但是通过后续钩子执行和执行会产生如下日志消息|562460|Error+resolving+case+of+'X:\the\path\to\theworkingcopy'|562461|因此，我将WORKING_COPY更改为使用UNC路径，如：|562462|\\servername\DRIVELETTER$\the\path\to\theworkingcopy|562463|仍然存在相同的问题，但我认为服务(对于这两种服务)都需要以网络特权运行，因此我将服务“登录As”更改为svn服务器和apache的域帐户。|562464|我遇到的另一个问题是为服务“以用户身份登录”设置域。我使用了域用户，但域使用了通配符，例如".\theuser“|562465|然后就成功了。|562466|至于这是一个脆弱的解决方案，我同意CI是一个更好的方法。尽管我们对UNC的svn更新是(1)文档化的，(2)现在正在工作，(3)它不太可能在不久的将来改变--正如UNC所指出的--它并没有分离出不同的关注点。|562467|entityMap^0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|12|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|13|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|14|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|15|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|16|8|@]|9|@]|A|$G|H]]|$1|Q|3|R|5|6|7|17|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|18|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|19|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1A|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|Z|$]]

two issues I ran into were (1) paths and (2) permissions. Our old setup included collabnet subversion server 1.5.6 and apache 2.2 on Windows 2008 R2 (it's now wandisco 1.7.2 / apache2.2 on Win 2008 R2). 

initially, I had the path as a mapped drive and the subversion and apache services running as the Local System account. So, we had something like:

<pre><code>SET WORKING_COPY=X:\the\path\to\theworkingcopy
</code></pre>

Running it via CLI was fine, but commiting and executing via subsequent hook resulted in log message like

<pre><code>Error resolving case of 'X:\the\path\to\theworkingcopy'
</code></pre>

So, I changed WORKING_COPY to use a UNC path such as:

<pre><code>\\servername\DRIVELETTER$\the\path\to\theworkingcopy
</code></pre>

Still same problem, but I figured the services (for both) needed to run with network privileges, so I changed the service "Log On As" to a domain account for the svn server and apache.

One other issue I ran into was setting the domain for the services' "Log On As" user. I used a domain user, but used a wildcard for the domain, e.g. ".\theuser"

Then it just worked.

As far as this being a brittle solution, I'd agree that CI is a better way to go. Even though our svn update over UNC is (1) documented and (2) works now and (3) it's unlikely to change in the near future - as thekbb noted - it doesn't separate concerns.

I've got Collabnet SVN server installed on windows. Additionally, I have implemented a post-commit hook that should update a working copy "B" of a project when I commit to the repository from a working copy "A". Working copy "B" resides on a network drive [H -> \\ip-address\users\myDirB ]:

<ul>
<li>Now when I specify the line of code below, in my post-commit hook and commit a change-set from working Copy "A":</li>
</ul>

<code>SET WORKING_COPY=H:/myDirB</code>

I get the error:
svn post-commit hook : "error resolving case" 

<ul>
<li>Alternatively if I specify:
<code>SET WORKING_COPY=//ip-address/users/myDirB</code></li>
</ul>

I get the error:

"skipped \ip-address\users\myDirB""

What am I doing wrong? Cheers.

Please note :
* Collabnet Subversion server is installed on my C: drive

<ul>
<li>it's running as a service account with full privileges over the network directory I want to update automatically via the post-commit hook i.e - \\ip-address\users\myDirB*</li>
<li>I also have the path \\ip-address\users\myDirB mapped on to H: drive</li>
</ul>

svn post-commit hook : "error resolving case" & "skipped \\ip-address\users\myDir"" messages

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我在windows上安装了Collabnet SVN服务器。此外，我还实现了一个后提交钩子，当我从工作副本"A“提交到存储库时，应该更新项目的工作副本"B”。工作拷贝"B“驻留在网络驱动器H -> \ip地址\user\myDirB上现在，当我在post-钩子中指定代码行时，从工作副本"A":中提交一个更改集。SET ...

问svn后提交钩子：“错误解决案例”&“跳过\\ip-地址\user\myDir”消息
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问svn后提交钩子：“错误解决案例”&“跳过\\ip-地址\user\myDir”消息EN