CI 服务器、lunt 构建或 Jenkins
我的公司目前使用 lunt build 作为 CI 服务器。 Hudson 现在分叉给 Jenkins，对我来说似乎非常强大。我很快就在 tomcat 上安装了它，GUI 似乎对于设置作业非常强大，此外还有超过 400 个开发者插件并且还在不断增加！
我想问是否可以使用 Jenkins 进行 POC。
你们中有人有这两种方法的经验吗？或者知道我在提交提案时可以使用的优缺点吗？
谢谢， 谢恩.
My company currently uses lunt build as CI server. Hudson now forked to Jenkins, seems pretty powerful to me. I quickly installed it on tomcat, and the GUI seems to be quite powerful for setting up jobs, plus there is over 400 developer plugins and counting!
I was going to ask is it possible to do a POC with Jenkins.
Do any of you guys have experience with both or know the pros and cons i can use when i submit my proposal?
Thanks,
Shane.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我们小公司的软件团队在使用 Luntbuild 三年后于 2010 年 1 月从 Luntbuild 切换到 Jenkins（née Hudson）。每个开发人员（包括一名经理）都认为 Jenkins 更干净、更简单且更易于使用。
我发现 Jenkins 中的作业（构建）更容易设置和配置，特别是对于从不同存储库 URL 构建的项目。文档都不是这两个项目的强项，但 Luntbuild 的文档似乎更大量，但实用性较差。詹金斯的社区充满活力。
除了我的个人经验之外，您可能还希望考虑标题为持续集成软件比较的维基百科文章。
Our small company's software team switched from Luntbuild to Jenkins (née Hudson) back in January, 2010, after using Luntbuild for three years. Every developer, including one manager, agrees that Jenkins is cleaner, simpler, and easier to use.
I found jobs (builds) much easier to set up and configure, in Jenkins, especially for projects built from different repository URLs. Documentation is neither project's strong-suit, but Luntbuild's seems more voluminous while being less useful. Jenkins' community is vibrant.
Beyond my personal experience, you may wish to consider the Wikipedia article titled Comparison of Continuous Integration Software.
最好的选择是浏览实际的 Jenkins CI 站点。以下是一些可能对您的情况有所帮助的链接。
https://wiki.jenkins-ci.org/display/JENKINS/Meet+Jenkins
该页面上有一个“测试驱动”Jenkins 的位置。听起来您已经设置了一个 Jenkins 实例，您也可以向其中添加几个“虚拟”构建。
此外，您可能有疑问的其他所有内容都可以在 Jenkins wiki 中找到：
https:// wiki.jenkins-ci.org/display/JENKINS/Home
希望这会有所帮助。
Your best bet is to poke around on the actual Jenkins CI site. Here's a few links that might help your case.
https://wiki.jenkins-ci.org/display/JENKINS/Meet+Jenkins
There's a spot to "test drive" Jenkins on that page. It sounds like you already set up a Jenkins instance, you could possibly add a couple "dummy" builds to that as well.
Also, everything else you might have questions about could be found in the Jenkins wiki:
https://wiki.jenkins-ci.org/display/JENKINS/Home
Hope this helps.