系统间缓存解决方案的持续集成
我正在使用 Intersystems Cache 从头开始一个项目。 我想为该项目设置一个持续集成服务器。 缓存具有单元测试库，因此想法是将源导入到测试数据库中，构建源，根据版本控制系统（ClearCase）中的更改在缓存终端中运行单元测试。
除了Cache Objectscript 之外，肯定还需要构建一些java 代码。 其他技术可以稍后添加。 因此，我需要一个不局限于某一特定技术并且易于扩展的持续集成工具。 我过去曾使用 CruiseControl 来构建 java 解决方案，但那已经是很久以前的事了，我想知道从那以后是否没有更好的解决方案可用。
什么是最好的（希望是免费的）持续集成产品，最容易扩展不同的技术？
I am starting a project from scratch using Intersystems Cache. I would like to setup a Continuous Integration Server for the project. Cache has unit test libraries, so the idea is to import source into a test database, build the source, run unit tests in the cache terminal, based on changes in the version control system (ClearCase).
Apart from Cache Objectscript, there will definitely be some java code that needs to be built as well. Other technologies could be added later. So I need a Continuous Integration tool that is not bound to one specific technology and that is easily extendible. I have used CruiseControl for building java solutions in the past, but that has been quite some time ago and I am wondering if no better solution is available since.
What is the best (and hopefully free) Continuous Integration product, that is easiest to extend for different technologies?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我建议查看 Hudson。 它非常容易尝试，因为它是作为可执行 jar 提供的。 它还支持插件，因此它可能更适合扩展和自定义。 Hudson 已经有很多非常方便的插件。 它的 ClearCase 支持是通过插件实现的。 甚至还有一个插件可以在您的构建过程中启动和停止 VMWare 虚拟机，这可能会引起您的兴趣，具体取决于您计划如何处理数据库服务器“需求”。
I'd recommend looking at Hudson. It's insanely easy to try out as it is delivered as an executable jar. It also supports plugins so it may be better suited to extension and customization. There are also a good deal of very handy plugins for Hudson already out there. Its ClearCase support comes via a plugin. There's even a plugin to start and stop VMWare virtual machines from within your build process which may be of interest depending on how you're planning on handling your database server "needs."
我在以下截屏视频中构建了一个临时的持续集成服务器： http://www.ensemblisms.com/episodes /2
I have built a makeshift Continuous Integration Server in the following screencast: http://www.ensemblisms.com/episodes/2
雷蒙德·罗斯滕伯格！！
我目前正在测试一个用于持续集成我们的解决方案的堆栈，该堆栈是在 Caché 中开发的，我正在测试的堆栈现在包括使用 Git + TortoiseGit 的版本控制源代码（带有一个名为“cache-tort-git”https://github.com/intersystems-ru/cache-tort-git/wiki 特定于Caché ）用于本地版本控制，BitBucket 用于远程版本控制。
为了持续集成，我使用 Jenkins（Hudson 的演变），其任务是下载更新的源代码，然后运行 COS 脚本来执行以下任务：
Raymond Roestenburg!!
I am currently testing a stack for continuous integration of our solution is developed in Caché , the stack I'm testing now includes versioning source code using Git + TortoiseGit (with a plugin called "cache-tort-git "https://github.com/intersystems-ru/cache-tort-git/wiki specific to Caché ) for local versioning and BitBucket for remote versioning.
For continuous integration I'm using the Jenkins (evolution of the Hudson) , with a job that downloads the updated source code and after runs a COS script that does the following tasks: