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

Eric Minick etm at urbancode.com
Tue Feb 6 23:56:22 CST 2007


The key is artifact sets. So you would have an artifact set (or several) 
for each platform.

-- Eric

Chad Loder wrote:

>On Tue, Feb 06, 2007 at 04:15:26PM -0700, Eric Minick wrote:
>  
>
>>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.
>>    
>>
>
>Eric,
>
>Interesting approach. I can see how this would be an elegant way to
>do the workflow. However, I have to think about how I could do this
>without mixing up artifacts from the two different systems.
>
>It's food for thought. Thanks :)
>
>	c
>
>  
>
>>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
>>>
>>>
>>>      
>>>
>>_______________________________________________
>>Anthill-pro mailing list
>>Anthill-pro at lists.urbancode.com
>>http://lists.urbancode.com/mailman/listinfo/anthill-pro
>>
>>    
>>
>_______________________________________________
>Anthill-pro mailing list
>Anthill-pro at lists.urbancode.com
>http://lists.urbancode.com/mailman/listinfo/anthill-pro
>  
>



More information about the Anthill-pro mailing list