Using scripts
Scripting allows python scripts to be used to automate project configuration in Automation Builder. Parameters can be added to scripts, so that a generic script can be customized before execution. The user can add a script to most parts of the device tree. A script can be started either from the user interface (by a command or with the python scripting editor) or from the Windows command line and is saved with the project.
With the scripting feature commands or complex program operations can be automated.
Examples of use cases:
-
Integration of Automation Builder in automatic build server environments:
-
continuous integration (CI)
-
continuous delivery (CD)
-
continuous testing
-
-
Integration with third party software, for example:
-
code generators
-
creation of projects that are custom tailored to a specific machine configuration
-
-
Creation of documentation
-
Updating of libraries: Setting of project information during the release process
-
Automatic testing: Mostly in connection with the Professional Test Manager
-
Outputting variables via monitoring APIs
Licensing
A valid license is required to use the scripting. If you open a project with the existing script object without a valid license, you are not allowed to add or edit the scripts. However, the scripts are not removed from the project.
Scripting language
The Automation Builder scripting language is modular and based on IronPython. For this purpose, the Automation Builder “ScriptEngine” component combines the IronPython interpreter with the Automation Builder development environment which makes the extensive python framework libraries available including file access in networks and much more.