Custom configuration allows the git environment to be configured during deployment and to alter what occurs after the deployed environment has been updated by git.
There are two exit points provided in the form of PowerShell scripts to be run by the Git Deployment Hub:
This script is run as soon as the trigger is received from GitHub, before the git pull is executed. The default script stops all processes running in the configuration. One use of this script is to alter the git environment before the pull is done, like changing the branch.
This script is run after the git pull has been executed. A default script is provided. This runs the Package Install to install and upgrade any application table and web page changes.
This file is generated by the Package Build and contains the list identifier which is used to set the Application name. This is the application that will be installed. The projectFolder setting in web.config does not affect which Package is installed.
The partition will also be added to this file in an upcoming release.
Changes will be overwritten, so it is not used for customization, and is included here to provide a more complete understanding of the deployment process.
This file is used to override x_run parameters. Only one setting is required and that is INST=MSI. All others may be set by the Developer in the Deployment Tool Package. One common use is to set the tracing flags. It has the same format as the x_lansa.pro file
There is a third script, SmokeTest.ps1. A default script is provided. This script is manually executed from the Git Deployment Hub user interface using the Smoke Test button. It is used to test that the setup is correct. By default it displays the git status, the remote system it's connecting to and performs a git pull.
The default scripts are in the Visual LANSA Development Environment in the autodeploy directory. You may customize the scripts in this directory or copy them into the application's autodeploy directory. For example, if Visual LANSA is installed into c:\program files(x86)\lansa and the list being deployed has an identifier of DEMO then the path of the folder is
This allows for per project customization.
All the scripts are automatically deployed.