This is so simple that I’ll just start this post with the 3 easy steps.  Then I’ll throw in some screenshots for good measure. 

1.  Setup a single build stream and a different workspace for each of the targeted platforms

2.  Before running a build, re-parent the build stream to the code stream to be built

3.  Update the workspaces and kickoff the build on each platform.

Simple, eh?

Now let’s drill down a bit with what this looks like in the StreamBrowser.  Let’s say we want to build different versions of AccuRev across 4 different platforms (Linux, MAX, Unix, Windows).

I have created a build stream with a workspace for each of those platforms (Step 1).  The physical location of the workspace is located on the approriate build server.  In addition, the private workspace contains any platform specific configuration files necessary for the build.

In this example, I am performing a build from the Accurev_INT stream.  Something you might want to do in a continuous integration environment.  As changes are promoted by the developers, the build automatically kicks off on each platform.

Now let’s say I decide to do a build for the Accurev 4.5.3 release for all platforms.  With a single command, I will re-parent the build stream to the AccuRev_4.5.3 snapshot (Step 2).

accurev chstream -s Build -p Accurev_4.5.3

>

After performing an update on the workspace and I can now run my build scripts (Step 3) and just like that, we’ve performed builds on all the platforms.

 Can you make use of this technique in your organization?