[Anthill-pro] AHP 3.4.10 Setting properties at project level
Eric Minick
etm at urbancode.com
Wed Mar 19 13:14:25 CST 2008
Mathew,
As an alternative, you could add a variable to each of these agents called
"shell_extension". On unix machines it would resolve to .sh and on windows,
.bat.
Then you would just execute script.${shell_extension} .
Does that seem like a workable approach?
-- Eric
On 3/19/08, Mathew Joseph <mjoseph at bravurasolutions.com> wrote:
>
> Hi There,
> I want to be able to change the script that I call based on the agent
> OS. i.e. script.bat if its windows and script.sh if its linux. The agent
> has properties to distinguish what OS it is using.
> I presume this would be a 3 step process.
>
> Step 1: Define a property at the workflow level called say, scriptName.
>
> Step 2: Have a evaluate script step in my job that checks the agent OS
> and assigns this property as script.bat or script.sh
>
> Step 3: The next step in the job (shell builder step) uses the property
> to run the script. Something like ${property:scriptName}
>
> Is this how you would approach this problem?
>
> Is it possible to modify a workflow/project level property from within a
> job?
>
>
>
> --
> Regards,
>
> Mathew Joseph
> Build & Release Engineer
> Bravura Solutions
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.urbancode.com/pipermail/anthill-pro/attachments/20080319/5c52f57b/attachment.htm
More information about the Anthill-pro
mailing list