TeamCity:Subversion VCS根与GitHub外部 [英] TeamCity: Subversion VCS root with GitHub externals

查看:158
本文介绍了TeamCity:Subversion VCS根与GitHub外部的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们有一个SVN仓库,其中有一些外部的东西托管在GitHub上。一切都在发展中; GutHub支持被SVN客户端访问。



问题在于TeamCity。它似乎是通过日期而不是通过修订得到外部。我们得到以下错误:

 未能构建修补程序#2.17.7081 {build id = 12},
VCS root:svn:https://xxx.xxx.xxx.xx/svn/iaw/trunk {instance id = 2,parent id = 1},由于错误:无法请求SVN日期修订:
svn :E200007:服务器不支持基于日期的操作
svn:E200007:请求的报告未知。
svn:E175002:'/cardeliverynetwork/csharp-apiclient.git/!svn/vcc/default'的报告:501未实现(https://github.com)
SVN服务器:https:/ /github.com/cardeliverynetwork/csharp-apiclient.git/trunk/src/CarDeliveryNetwork.Types
使用版本:2013年2月15日11:03:24上午
修订版本:7081_2013 / 02/15 11 :03:24 +0000

有谁知道如何强迫TeamCity简单地在外部获取HEAD? / p>

谢谢。

解决方案

我在Subversion中有一个外部的。



为了解决这个问题,我在我引用它的地方添加了外部的确切版本号。



基本上就是这样



之前的参考资料: \ gitserver \ repository \folder external code

参考后: \gitserver\repository\folder @ 2013 external



请尝试在你引用的Subversion文件夹的属性中添加这样的修订。如果您转到Subversion中文件夹的属性并在高级模式下执行属性编辑,可以像这样编辑。



希望它能起作用,尽管不太确定!

>

We have an SVN repository with some externals hosted at GitHub. All is well in development; GutHub supports being accessed by an SVN client very well.

The problem is with TeamCity. It appears to get the externals by date rather than by revision. We get the following error:

   Failed to build patch for build #2.17.7081 {build id=12}, 
   VCS root: svn: https://xxx.xxx.xxx.xx/svn/iaw/trunk {instance id=2, parent id=1}, due to error: Cannot request SVN dated revision: 
   svn: E200007: Server does not support date-based operations
   svn: E200007: The requested report is unknown.
   svn: E175002: REPORT of '/cardeliverynetwork/csharp-apiclient.git/!svn/vcc/default': 501 Not Implemented (https://github.com)
   SVN server: https://github.com/cardeliverynetwork/csharp-apiclient.git/trunk/src/CarDeliveryNetwork.Types
   Used rev: Feb 15, 2013 11:03:24 AM
   Rev text:7081_2013/02/15 11:03:24 +0000

Does anyone know how to force TeamCity to simply get HEAD on externals?

Thanks.

解决方案

It seems like I faced a similar issue when I had an external in Subversion itself.

To solve the same I added the exact revision number of the external in the place where I referred it.

It was basically like this

Reference Before: \gitserver\repository\folder external

Reference After : \gitserver\repository\folder@2013 external

Please try adding the revision like this in the properties of the Subversion folder you are referring. This can be edited like this if you go to properties of the folder in Subversion and do property Edit in Advanced mode.

Hope it works though not so sure!

这篇关于TeamCity:Subversion VCS根与GitHub外部的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆