持续集成& eclipse插件开发
我正在开发一组 Eclipse 插件，并且我有几个 JUnit 插件测试，它们实际上启动了 Eclipse 的另一个实例，创建一个模拟工作区和一个模拟项目，并对它们运行各种操作。我想把它放在持续集成上，但我不知道从哪里开始。我正在使用 Hudson，是否有任何插件可以让这变得更容易？这些测试可以在无头模式下启动 eclipse 或者 CI 服务器上的其他东西吗？指针将不胜感激。
I am developing a set of eclipse plugins, and I have several JUnit plugin tests that actually start another instance of eclipse, create a mock workspace and a mock project and runs various operations on them. I want to put that on continuous integration and I am at loss as to where to start. I am using Hudson, would there be any plugins that makes that easier? Can those tests launch eclipse in headless mode or something on the CI server? Pointers would be much appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我认为目前构建基于 Eclipse 的软件的最佳解决方案是 Tycho - 它基于 Maven 并使用标准 Eclipse 文件（如清单、目标平台、产品定义）。我使用此博客的介绍开始使用它： http://mattiasholmqvist.se/2010/02/building-with-tycho-part-1-osgi-bundles/，效果非常好。我们还使用 Hudson，并且由于 Tycho 是基于 Maven 的，因此 Hudson 集成很简单，只需调用 Maven 即可工作，Hudson 开箱即用地支持 Maven。
I think the best solution for building Eclipse-based software currently is Tycho - it is based on Maven and uses your standard Eclipse files (like manifest, target platform, product definition). I got started with it using an intro from this blog: http://mattiasholmqvist.se/2010/02/building-with-tycho-part-1-osgi-bundles/, and it worked really well. We also use Hudson, and since Tycho is Maven-based, Hudson integration was trivial and worked simply by calling Maven, which Hudson supports out of the box.
据我所知，Buckminster试图解决这些问题：你可以创建描述符，然后Buckminster可以执行你的任务。
对于 Hudson，有一个 Buckminster 模块，可以帮助执行 Buckminster 构建。
As far as I know, Buckminster tries to solve these problems: you can create descriptors, and then Buckminster can execute your tasks.
For Hudson there is a Buckminster module, that helps executing the Buckminster builds.
也许这可以帮助您避免插件测试？ ;) 我喜欢避免它们...通过使用模拟对象...
http://blog.srvme.de/2010/12/10/mock-eclipse-ifile/
maybe this helps you to avoid plugin tests? ;) i like to avoid them... by using mock objects...
http://blog.srvme.de/2010/12/10/mock-eclipse-ifile/