Team City 构建 Orchard CMS 失败

发布于 2025-01-08 15:48:26 字数 1303 浏览 0 评论 0原文

我是 Orchard 和 MVC 3 的新手。现在,我正在尝试在 Team City 下构建我的解决方案。但它并没有构建成功。

我已经从果园的网站下载了整个源代码。目录结构为

OrchardSite(根文件夹) ->Lib(根目录的子文件夹) ->Src(根的子文件夹)

这两个文件夹都是我的存储库的一部分。

Team City 中的构建失败并抱怨无法找到任何依赖项。 错误日志的快照:

[12:09:09]: Orchard\Orchard.Framework.csproj (13s)
[12:09:10]: [Orchard\Orchard.Framework.csproj] CoreCompile (12s)
[12:09:10]: [CoreCompile] Csc (12s)
[12:09:21]: [Csc] ContentManagement\ContentItemBehavior.cs(2, 7): error CS0246: The type or namespace name 'ClaySharp' could not be found (are you missing a using directive or an assembly reference?)
[12:09:21]: [Csc] ContentManagement\ContentItemBehavior.cs(5, 40): error CS0246: The type or namespace name 'ClayBehavior' could not be found (are you missing a using directive or an assembly reference?)
[12:09:21]: [Csc] ContentManagement\DefaultContentDisplay.cs(5, 7): error CS0246: The type or namespace name 'ClaySharp' could not be found (are you missing a using directive or an assembly reference?)
[12:09:21]: [Csc] ContentManagement\IContentBehavior.cs(1, 7): error CS0246: The type or namespace name 'ClaySharp' could not be found (are you missing a using directive or an assembly reference?)

不确定需要做什么。有人可以帮我吗?

PS 我不想让这篇文章写得太长 - 所以,如果有任何你需要知道而我错过的事情,请告诉我。谢谢!

I am new to Orchard and MVC 3. Now, am trying to build my solution under Team City. But it is not building successfully.

I had downloaded the whole source from orchard's website. The directory structure is

OrchardSite (Root Folder)
->Lib (Root's Sub Folder)
->Src (Root's Sub Folder)

Both these folders are a part of my repo.

The build in Team City fails and complains of not being able to find any dependencies.
A snapshot of the error log :

[12:09:09]: Orchard\Orchard.Framework.csproj (13s)
[12:09:10]: [Orchard\Orchard.Framework.csproj] CoreCompile (12s)
[12:09:10]: [CoreCompile] Csc (12s)
[12:09:21]: [Csc] ContentManagement\ContentItemBehavior.cs(2, 7): error CS0246: The type or namespace name 'ClaySharp' could not be found (are you missing a using directive or an assembly reference?)
[12:09:21]: [Csc] ContentManagement\ContentItemBehavior.cs(5, 40): error CS0246: The type or namespace name 'ClayBehavior' could not be found (are you missing a using directive or an assembly reference?)
[12:09:21]: [Csc] ContentManagement\DefaultContentDisplay.cs(5, 7): error CS0246: The type or namespace name 'ClaySharp' could not be found (are you missing a using directive or an assembly reference?)
[12:09:21]: [Csc] ContentManagement\IContentBehavior.cs(1, 7): error CS0246: The type or namespace name 'ClaySharp' could not be found (are you missing a using directive or an assembly reference?)

Not sure what needs to be done. Can someone please help me out?

P.S. I don't want to make this post too long - so, if there is anything that you need to know and I have missed out, please let me know. Thanks!

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

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

发布评论

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

评论(1

虚拟世界 2025-01-15 15:48:26

我们使用 Team City 作为我们的持续集成。您可以看一下我们的配置:http://teamcity.codebetter .com/project.html?projectId=project143&tab=projectOverview

这是我们设置的副本:

常规设置
姓名: *
描述:
内部版本号格式:*
格式可能包含“{0}”作为构建计数器值的占位符,例如 1.{0}。它还可能包含对任何可用参数的引用,例如,VCS 修订号:%build.vcs.number.*%。
注意:所有替换后内部版本号的最大长度为 256 个字符。

构建计数器:* 重置计数器
工件路径:
编辑工件路径:

隐藏
用于构建工件的新行或逗号分隔路径。支持 ant 风格的通配符,例如 dir/*/.zip 和目标目录,例如 *.zip => winFiles,unix/distro.tgz => linuxFiles,其中 winFiles 和 linuxFiles 是目标目录。
如果出现以下情况,则构建失败:
构建进程退出代码不为零
至少一项测试失败
构建运行程序记录错误消息
它运行的时间超过分钟
检测到内存不足或崩溃(仅限 Java)
构建选项:启用挂起构建检测
启用状态小部件
限制同时运行的构建数量(0 - 无限制)

Checkout Settings
VCS结帐模式:
结账目录:
留空以使用代理上的默认签出目录。

构建前清理所有文件:
VCS 标签
VCS标记方式:不标记
仅成功
总是
标签图案:
选择要标记的 VCS 根:Orchard Mercurial (CodePlex) (1.x)

构建步骤
跑步者类型:
MSBuild 文件的运行程序
步骤名称:
您可以指定构建步骤名称以将其与其他步骤区分开。
构建文件路径:*
指定的路径应该相对于结帐目录。

工作目录:
可选,指定是否与结帐目录不同。

MSBuild 版本:
MSBuild 工具版本:
运行平台:
目标:
输入以空格或分号分隔的目标。

命令行参数:
在 MSBuild.exe 中输入其他命令行参数。

减少测试失败反馈时间:首先运行最近失败的测试
.NET 覆盖范围
.NET覆盖工具:

构建触发器参数说明
VCS 触发静默期:300 秒(默认)

We use Team City as our continuous integration. You can probably take a peek at our configuration: http://teamcity.codebetter.com/project.html?projectId=project143&tab=projectOverview

Here is a copy of our settings:

General Settings
Name: *
Description:
Build number format: *
Format may include '{0}' as a placeholder for build counter value, for example 1.{0}. It may also contain a reference to any available parameter, for example, VCS revision number: %build.vcs.number.*%.
Note: maximum length of a build number after all substitutions is 256 characters.

Build counter: * Reset counter
Artifact paths:
Edit artifact paths:

Hide
New line or comma separated paths to build artifacts. Support ant-style wildcards like dir/*/.zip and target directories like *.zip => winFiles,unix/distro.tgz => linuxFiles, where winFiles and linuxFiles are target directories.
Fail build if:
build process exit code is not zero
at least one test failed
an error message is logged by build runner
it runs longer than minutes
an out of memory or crash is detected (Java only)
Build options: enable hanging builds detection
enable status widget
Limit the number of simultaneously running builds (0 - unlimited)

Checkout Settings
VCS checkout mode:
Checkout directory:
Leave blank to use default checkout directory on an agent.

Clean all files before build:
VCS Labeling
VCS labeling mode: Do not label
Successful only
Always
Labeling pattern:
Choose VCS roots to label: Orchard Mercurial (CodePlex) (1.x)

Build Step
Runner type:
Runner for MSBuild files
Step name:
You can specify build step name to distinguish it from other steps.
Build file path: *
Specified path should be relative to the checkout directory.

Working directory:
Optional, specify if differs from the checkout directory.

MSBuild version:
MSBuild ToolsVersion:
Run platform:
Targets:
Enter targets separated by space or semicolon.

Command line parameters:
Enter additional command line parameters to MSBuild.exe.

Reduce test failure feedback time: Run recently failed tests first
.NET Coverage
.NET Coverage tool:

Build Trigger Parameters Description
VCS Trigger Quiet period: 300 seconds (default)

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