用于Flex的持续集成服务器 [英] Continuous integration servers for Flex

问题描述

您使用哪个CI服务器进行Flex？我的主要竞争对手目前是

• Hudson


• TeamCity






两者似乎都在一般水平上受欢迎，但是你有使用Flex开发中的一个或两个的直接经验吗？或者你会推荐一些其他工具吗？

解决方案

我们使用Hudson。





我们正在开发一个Java / Flex应用程序。
Ant是构建系统。 SVN源代码管理器。





我们有一个编译mxml和ActionScript的ant任务。





Hudson位于虚拟机上，SVN位于另一个虚拟机上，构建版本存档/部署在第三个。





Hudson按时调用ant任务。 （每次提交flex代码后）





没有单元测试调用flex。对于java是的。但是你也可以通过ant脚本调用FlexUnit（或FlexMonkey）。





运行测试后，构建部署在另一个VM上。





它没有痛苦。你只需要有一个工作的ant任务来编译你的应用程序的flex部分。





如果你使用maven，hudson也处理它。他也可以播放.bat或.sh脚本并检查输出。





关于您的teamcity / hudson之间的选择，我认为他们两个非常接近。




Which CI server do you use for Flex? My main contenders are currently

• Hudson
• TeamCity

Both seem to be popular on the general level but have you got some direct experience with using one or both with Flex development? Or would you recommend some other tool?

解决方案

We use Hudson.

We are working on a Java/Flex application. Ant is the build system. SVN the source manager.

We have a ant task for compiling the mxml and the actionScript.

Hudson is on a virtual machine, SVN on another, and the build are archived / deployed on a third.

Hudson call the ant task on due time. ( After each commit on the flex code )

No Unit test are call for flex. For java yes. But you can call FlexUnit ( or FlexMonkey ) throught a ant script as well.

After running the test, the build is deployed on another VM.

It's run with no pain. You just have to have a working ant task for compilling the flex part of your application.

If your using maven, hudson handle it too. He can also play .bat or .sh script and check the output.

About your choice between teamcity / hudson, i think the two of them are very close.

这篇关于用于Flex的持续集成服务器的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！