[Anthill-pro] Running non-originating workflows in same environment as originating

[Eric Minick]

Chad,

Right now you're stuck picking. What we'll suggest in 3.2 is that you 
put both the windows and linux test machines in a single Test 
environment and use an agent selection script to match the OS of the 
test agent to the OS of the test machine. This will be an advanced Agent 
Filter option.

I think the assumption that Anthill is making right now is that you 
wouldn't have a Linux build workflow and a Windows build workflow. 
Instead you'd have a linux build job and a windows build job. Your 
single "Build Workflow" would be comprised of two jobs doing the two 
builds in parallel and gathering the build results for each as different 
artifact set. Your single 'Test' workflow would deploy the two builds 
out to the two environments and running the linux tests on the linux box 
and the Windows tests on the Windows box.

Regards,

Eric

Chad Loder wrote:

>Hello.
>
>I have two originating workflows: a Linux Build workflow that runs on the Linux
>build farm and a Windows Build workflow that runs on the Windows build farm.
>
>I have a non-originating workflow called Unit Test that runs unit tests on the
>compiled code from the previous workflow. When I choose to run this workflow
>on an existing Build life, I have to choose the environment explicitly.
>
>Is there a way to automatically force a non-originating workflow to run in
>the same environment as the originating workflow? It seems like a natural
>thing to want to do.
>
>Thanks,
>	c
>_______________________________________________
>Anthill-pro mailing list
>Anthill-pro at lists.urbancode.com
>http://lists.urbancode.com/mailman/listinfo/anthill-pro
>  
>