[Anthill-pro] Using properties as a condition to bypass a step

[Alexandre Borgia]

The way I’m doing it right now is either by putting the logic into the build scripts whenever possible (and pass the property) or use a general Shell step where I can use constructs like these to define what must be executed:

 

${bsh:”1”.equals(PropertyLookup.get(“doSomething”)) ? “doSomething.exe” : “echo skipped step doSomething …” }

 

… maybe not the a great syntax to look at but it works fairly well.

 

The problem with using different jobs is that it won’t necessarily run on the same agent or in the same context and might give some extra overhead (i.e. need to sync the repository again etc.)

 

            - Alexandre Borgia

 

________________________________

De : anthill-pro-bounces at lists.urbancode.com [mailto:anthill-pro-bounces at lists.urbancode.com] De la part de Uldis Karlovs-Karlovskis
Envoyé : 10 avril 2008 02:10
À : 'AnthillPro user and support list.'
Objet : RE: [Anthill-pro] Using properties as a condition to bypass a step

 

I`ve found an only way to accomplish this by splitting those steps into Jobs, so after then You can use Job Precondition scripts.

 

Regards,

Uldis, C. T. Co

uldis.karlovs-karlovskis at ctco.lv <mailto:uldis.karlovs-karlovskis at ctco.lv> 

 

-----Original Message-----
From: anthill-pro-bounces at lists.urbancode.com [mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Tyler Andreasen
Sent: ceturtdiena, 2008. gada 10. aprīlī 0:43
To: anthill-pro at lists.urbancode.com
Subject: [Anthill-pro] Using properties as a condition to bypass a step

 

I have a job with several tasks.  I want to have a Boolean property (0 or 1) such that if set to 0, certain steps in a job will NOT run.  Is there any practical way to do this using properties?  Or is there another way.  

 

Thanks, 

T. Andreasen

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.urbancode.com/pipermail/anthill-pro/attachments/20080410/d0e3c2b8/attachment.htm