Your browser was unable to load all of the resources. They may have been blocked by your firewall, proxy or browser configuration.
Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again.

QuickBuild

QB3.0.14: More builtin scriptlets #1563

#1
scastria ·
I like all of your builtin scriptlets available with certain step parameters, like Execute Condition. This saves me from writing QB scripts lessening my chance of making a mistake and making upgrades more portable. I think you need one more. A NOT operator. You essentially have AND and OR, but no NOT. The reason that NOT is useful is when I want to run something when a variable evaluates to false. You have "variable evaluates to true", but not false. Therefore, I have to use the less rigid "script evaluates to true" and put a ! in front of it. So either you could add a "variable evaluates to false" OR add a more generic NOT operator. I prefer the latter since it is more flexible. Thanks.
  • replies 4
  • views 2505
  • stars 0
#2
robinshen ADMIN ·
NOT operation will be added in QB4. Thanks.
#3
drdt ·
I know not necessary, but I wanted to add my vote to this! It would make the evaluations much more powerful.
#4
scastria ·
Another idea to remove some hand coded scripting that I currently use would be step name and status codes. For example, sometimes I need to run a step only if some previous step in the workflow was successful. So you could add a step scriptlet that was, "Step has status code" where it will allow you to pick the step name from a drop down combo and then pick the status from "successful", "failed", "idle", etc. I would imagine you might have to leave the step name as an empty text box, since repeat parameters would make it impossible for you to produce a combo box with all possible choices.

Here is an example script that I use that could benefit from a builtin scriptlet:

!steps.get("master>platforms>platform-linux").idle
#5
robinshen ADMIN ·
Filed as improvement request http://track.pmease.com/browse/QB-1033
Log in to reply