如何在为多个平台构建时使用hudson [英] How to use hudson when building for multiple platforms

问题描述

现在我们正在为Win32平台构建一些C ++应用程序。我们将很快移植到Linux，然后可能更多（32和64位）。

什么是标准做法，您是否在自己的平台上使用多个哈德森服务器来执行构建，或者hudson服务是否创建VM并进行构建？ p>

我不清楚这是最好的实践方法。

理想情况下，我只想要一个一堆VM运行哈德森，然后根据需要启动构建。

有人可以指定我的资源吗？

解决方案

p>我们使用Hudson来管理用于多个操作系统的C / C ++（GNU C，GNU C ++，Watcom C）。对我们来说，软件是为Linux，Linux x64，QNX 4和QNX6构建的。我们设置的方式是：

• 运行Windows的Hudson服务器1个虚拟机


• 4 x VM，每个从属类型一个，因此我有4个Hudson奴隶 - QNX4，QNX6和Linux 32和Linux 64各1个。它们都在同一个服务器上运行，就像不同的VM，我们有面临没有问题。我们建立了100个项目，在4种系统类型之间几乎平分。

您不应该需要任何额外的硬件。有一个Hudson插件可以与VMWare虚拟机配合使用，启动它们并根据需要关闭它们。

我希望有帮助。

Right now we are building a number of C++ apps for Win32 platform. We will be soon porting to Linux and then maybe more (32 and 64 bits for both).

What is the standard practice , do you use multiple hudson servers each on their own platform to do a build, or does the hudson service create VMs and do builds?

It is not clear to me the best practical way to do this.

Ideally I just want one box with a bunch of VMs running hudson, and then it kicks off builds as needed.

Is there a resource someone can point me to for this?

解决方案

We use Hudson to manage C/C++ (GNU C, GNU C++, Watcom C) builds for multiple OSs. For us, software is built for Linux, Linux x64, QNX 4, and QNX6. The way we have it set up is:

• 1 x VM for the Hudson server, running Windows
• 4 x VMs, one for each slave type, so I have 4 Hudson slaves - 1 each for QNX4, QNX6 and Linux 32 and Linux 64. All of them are running on the same server, just as different VMs, and we have faced no problems. We build about a 100 projects, divided almost equally between the 4 system types.

You should not require any additional hardware. There is a Hudson plugin that works with VMWare VMs, to start them up and shut them down as required.

I hope that helps.

这篇关于如何在为多个平台构建时使用hudson的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！