Skip to content

KillAll extra actions

Choose a tag to compare

@pjanec pjanec released this 03 Jan 13:54
· 127 commits to 3.1 since this release

KillAll command can invoke extra actions on different machines

SharedConfig.xml

In the SharedConfig.xml, you can define the list of actions (tools) to take when the KillAll is invoked.

    <KillAll>
        <Tool HostId="m1" Name="BatchScript" Args="c:\kill-all-action-1.bat"/>
        <Tool HostId="m2" Name="PowershellScript" Args="c:\kill-all-action-2.ps1"/>
    </KillAll>

The HostId is mandatory, defines on what machine to run the tool...
The args are specific to the machine where the script runs.

LocalConfig.xml

On each machine where KillAll extra actions are to be run, the LocalConfig.xml file should contain the definition of apps (called Tools) that can be invoked during the KillAll.

For example, a tool for

  • running a batch script
  • running a powershell script
  • ...whatever other app
  <Tool
    AppIdTuple = "BatchScript"
    ExeFullPath = "[cmd.file]"
    CmdLineArgs = ""
    StartupDir = ""
  />

  <Tool
    AppIdTuple = "PowershellScript"
    ExeFullPath = "[powershell.file]"
    CmdLineArgs = ""
    StartupDir = ""
  />

You override the command line arguments passed to the tool from the SharedConfig.xml – for example to specify what script to run.