RTC 3.0 Build - multi platform environment

I would like to create a multi-platform build, say, Windows and Linux. I can define for each platform separate build definition and engine. The problem is that both builds work separately. There is no guarantee that they will be based on the same version of the source code, since each one will have its own snapshot. It can happen even if build requests for both builds will be issued simultaneously. Can I define such build the way they do in Hudson (www.hudson.org)? Hudson allows me to define various build steps and their dependencies. With Hudson we can define the whole build -deploy -test steps.


Thanks,

Yaron

Hi Yaron,

I don't know if there is an easy way to do that with RTC.

If you know Hudson you could use RTC and Hudson together. You can even publish Hudson build result URl's to the RTC Build result. Here is an article about how to integrate RTC and Hudson: https://jazz.net/projects/rational-team-concert/integrations/

In addition I have seen several work items for making the integration easier.

Hi Ralph,

Thanks for the quick response.
I am aware to the RTC - Hudson integration and we are using it for other project.

I would like to check whether we can accomplish this request without using Hudson.
I would like to supply to the project an end to end solution without using external tools like Hudson.

There are a variety of ways of using RTC to build a specific
configuration. First, create a snapshot of the configuration that you
want to build. Then you can configure a workspace with that snapshot,
and request a personal build with that workspace. Another is to
configure a stream with that snapshot, and request a team build on that
stream.

Or am I missing what you are trying to do here?

Cheers,
Geoff

On 6/27/2011 5:08 AM, yaron wrote:

I would like to create a multi-platform build, say, Windows and Linux.
I can define for each platform separate build definition and engine.
The problem is that both builds work separately. There is no
guarantee that they will be based on the same version of the source
code, since each one will have its own snapshot. It can happen even
if build requests for both builds will be issued simultaneously. Can
I define such build the way they do in Hudson (www.hudson.org)?
Hudson allows me to define various build steps and their
dependencies. With Hudson we can define the whole build -deploy -test
steps.


Thanks,

Yaron

Hi Geoff,

The scenario is creating a multiplatform build and then execute further steps such as a test script.
We would like to evaluate whether it can be accomplished without Hudson.
The flow is:
1. based on the stream we need to perform team build.
2. Windows Build.
3. Linux build.
4. If steps 2-3 succeed - start 5.
5. Execute test script.

The issue is that currently I do not know how to automate this logic scenario with RTC.
Moreover - steps 2-3 has different build ID with a different snapshot and repository workspace/sandbox.

With Hundon I can implement that "logical flow" using tasks.

Is there a way to implement it without Hundson?

Thanks,

Yaron

For this kind of scenario, we would normally use the BuildForge build
agent, which provides that kind of scriptability (and much more) ... but
that of course requires that you have BuildForge (:-).

Cheers,
Geoff

On 7/20/2011 4:23 AM, yaron wrote:

Hi Geoff,

The scenario is creating a multiplatform build and then execute
further steps such as a test script.
We would like to evaluate whether it can be accomplished without
Hudson.
The flow is:
1. based on the stream we need to perform team build.
2. Windows Build.
3. Linux build.
4. If steps 2-3 succeed - start 5.
5. Execute test script.

The issue is that currently I do not know how to automate this logic
scenario with RTC.
Moreover - steps 2-3 has different build ID with a different snapshot
and repository workspace/sandbox.

With Hundon I can implement that "logical flow" using
tasks.

Is there a way to implement it without Hundson?

Thanks,

Yaron