blocks|key|321118|text|我们有几乎相同的构建运行时间，可能在selenium上略少(我会说大约3x50分钟的运行时间，在firefox，即和opera上进行相同的站点测试)。我们的解决方案是投入更多的cpu，我们有一个由7个双核节点组成的集群bamboo环境。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|321119|我们发现，在与web容器/+selenium测试分离的盒子上运行selenium-rc和浏览器可以显着提高selenium的运行时间。|321120|entityMap|0|LINK|mutability|MUTABLE|url|http://www.atlassian.com/software/bamboo/^0|31|6|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

We have just about the same build runtimes, maybe slightly less on selenium (I'd say around 3x50 minutes runtime, same site tests on firefox, ie and opera). Our solution was to throw more cpu at it, and we have a clustered <a href="http://www.atlassian.com/software/bamboo/" rel="nofollow noreferrer">bamboo</a> environment of totally 7 dual-core nodes.

We found that running selenium-rc and the browser on a seperate box from the web-container/selenium test improved selenium runtimes quite significantly.

blocks|key|4386375|text|我正在使用GNU+make来自动化所有的事情。根据项目的不同，它需要2分钟到30分钟。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4386376|entityMap|0|LINK|mutability|MUTABLE|url|http://www.gnu.org/software/make/^0|5|8|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I'm using <a href="http://www.gnu.org/software/make/" rel="nofollow noreferrer">GNU make</a> to automate everything. Depending it takes from 2 minutes to 30 minutes depending on the project.

blocks|key|321141|text|Team+System:+1小时内完成所有任务|type|unstyled|depth|inlineStyleRanges|entityRanges|data|321142|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Team System: under 1 hour for everything

blocks|key|1028281|text|我假设你的项目由几个子项目组成。如果不是这样，您可能需要重构代码库，以便它可以这样做。通过这种方式，您可以选择只构建整个应用程序的特定部分，测试单个部分，然后在解决了正在处理的子项目上的错误后运行集成测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1028282|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I assume your project consists of several subprojects. If it does not you may want to refactor the code base so that it does. This way you can chose to only build specific parts of the overall application, test the individual part then run your integration tests when you’ve worked out the bugs on the subproject you are working on.

blocks|key|4386423|text|我们使用Hudson构建一个大型的C#解决方案，其中包含一些windows服务、web服务和可执行文件。大约有800个人通过MSTest.exe进行测试，每个构建大约需要12-15分钟。由于MSTest很慢，测试占据了很大的一部分。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4386424|为了减少时间，我们试图限制通过MSTest运行的程序集的数量，因为安装和拆除似乎需要一段时间。|4386425|编辑:我们的构建还部署到我们的cert+env，其中包括web服务、windows服务、可执行文件和数据库部署。只是为了给你一个范围的概念|4386426|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

We use Hudson to build a large C# solution containing a handful of windows services, web services, and executables. Around 800 or so tests via MSTest.exe and it takes about 12-15 minutes per build. Tests take up a large portion since MSTest is slooow.

To cut down on time we've tried to limit the number of assemblies produced to run through MSTest since the setup and teardown seems to take a while.

Edit: Our build also deploys to our cert env which includes web services, windows services, executables and database deployment. Just to give you an idea of scope

blocks|key|4386446|text|Erlang+Common+Test+-主要关注系统测试，而不是单元测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4386447|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Erlang Common Test - mostly focussing on System Tests as opposed to Unit Tests.

blocks|key|1023449|text|我们所有的自动化构建都是通过Team+City完成的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1023450|我们使用的自动化程度最高的项目是一个高效的编译器。我们的测试套件由大约20000个编译和运行的测试查询组成，这些查询在每次签入时都会运行。这通常需要一个小时的大部分时间，但是将完整的测试套件保存在构建机器上的RAM驱动器中(而不是每次都检查)，可以将测试时间缩短到几分钟。|1023451|每天晚上都会触发第二个构建，运行这些相同的测试，但在4个不同的配置文件下运行，同时在NCover下运行，它会生成代码覆盖率报告。这个场景需要几个小时，这就是为什么它是以夜间构建的方式完成的。同时生成其他内部报告，以确保一切正常运行。|1023452|对测试套件本身的更新是单独触发的，并签出到RAM驱动器，为下一次运行做好准备。否则，检查测试会占用大部分的构建时间。测试套件的一部分来自我们无法控制的远程CVS存储库，甚至在构建时间增加了几分钟的情况下查询更新，所以这也是在“更新测试”构建中完成的。这种松散耦合意味着我们不得不将此项目的构建限制在一台机器上，但由于反馈如此迅速，这并不是一个大问题。|1023453|事实证明，在保持代码库的高覆盖率的同时，尽可能快地保持“常规”测试构建是非常有帮助的。任何缓慢的测试(超过一秒左右)都会被拉到夜间构建中。在我们的例子中，将测试保存在RAM驱动器中真的很有帮助，尽管我们的场景相当专业。我想模拟你的数据库是最接近的等价物。我的建议是，通过删除任何“笨重的”或缓慢的测试来保持一个构建的“精简和平均”，允许一个快速的响应知道你可能没有破坏任何东西。其他构建可以在单独的机器上运行，或者在晚上运行，以保持快速构建的快速响应。|1023454|从长远来看，我们(对于另一个项目)最长的自动化构建有时需要一天以上的时间，尽管值得庆幸的是，它不需要定期运行。|1023455|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

All our automated builds are done with Team City.

The most automated project we work with is effectively a compiler. Our test suite consists of around 20000 test queries that are compiled and run, which is run on every checkin. This used to take the best part of an hour, but keeping the complete test suite in a RAM drive on the build machine (rather than checking it out each time) reduces this to a few minutes.

Every night a second build is triggered that runs these same tests, but under 4 different profiles, whilst running under NCover which produces a code coverage report. This scenario takes several hours, which is why it is done as a nightly build. Other internal reports are produced at the same time to ensure that everything is working as it should.

Updates to the test suite itself are triggered separately and checked out to the RAM drive ready for the next run. Checking the tests out was otherwise taking most of the build time. Part of the test suite comes from a remote CVS repository out of our control and even querying this for updates added a few minutes to the build time, so this is also done in the "Update tests" build. This loose coupling has meant that we have had to restrict builds of this project to one machine, but since feedback is so quick, this is not a big problem.

It has proved immensely helpful to keep the "regular" test build as fast as possible whilst retaining high coverage of the codebase. Any slow tests (more than a second or so) have been pulled through to the nightly build. In our case keeping the tests in a RAM drive has really helped, although our scenario is rather specialist. I guess that mocking your database is the nearest equivalent. My advice is to keep one build "lean and mean" by removing any "chunky" or slow tests, allowing a snappy response to know you probably haven't broken anything. The other builds can be run on separate machines, or at night in order to keep the response quick from the fast build.

For perspective the longest automated build we have (for another project) sometimes takes more than a day, although thankfully it is not one that needs to be run regularly.

blocks|key|4386540|text|不幸的是，在我目前的客户端，BuildForge+(来自ClearCase+SCC)：任何地方都需要一到三天。严重的。我真的不知道他们在构建中做了什么，也不知道为什么要花这么长时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4386541|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

At my current client, unfortunately, BuildForge (from ClearCase SCC): anywhere from one to three days. Seriosuly. I don't really know what they do in a build or why it takes so long.

My current project has 5 separate automated builds that kick off after each check-in: 
Unit Tests (DB calls mocked out): ~6 Minutes 
Integration Tests (just to the DB): ~40 Minutes 
Website 1 UI (Selenium, from UI to DB): ~80 Minutes 
Website 2 UI1 (Selenium, from UI to DB): ~90 Minutes 
Website 2 UI2 (Selenium, from UI to DB): ~100 Minutes 

We are using Maven2, JUnit and Selenium.

One strategy that I think will reduce drastically reduce Integration test time, is moving as many Integration tests as possible into the Unit Tests, and simply using the Integration project to test persistence to the DB.

I'm wondering what strategies you've found that have helped to reduce build times on large projects.

What automated build systems are you using? How long do your builds take?

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我目前的项目有5个独立的自动化构建，每次签入后都会启动：单元测试(模拟数据库调用)：大约6分钟集成测试(仅针对数据库)：约40分钟网站1 UI (Selenium，从UI到DB)：大约80分钟网站2 UI1 (Selenium，从UI到DB)：大约90分钟网站2 UI2 (Selenium，从UI到DB)：大约100分钟我们使用的是Maven2、JUnit和Selenium。我认为将大大减少集成测

问您使用的是哪些自动构建系统？您的构建需要多长时间？
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问您使用的是哪些自动构建系统？您的构建需要多长时间？EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问您使用的是哪些自动构建系统？您的构建需要多长时间？
EN