To build projects using the PBAutoBuild approach (the default mode), you can execute the PBAutoBuild250.exe file with the /f and related parameters. (Note that you can build all project types (including PowerBuilder C/S Application projects, PowerClient projects, and PowerServer projects)).
PBAutoBuild250 /f filename [/options]
/f parameter is required; the other parameters are optional.
For example,
PBAutoBuild250 /f c:\SalesDemo_cloud.json /l deploy.log /le error.log /lu unsupport.log /v "project1:1.0.0.1;project2:1.2.3.4" /vn "project1:1.0.0.1;project2:1.2.3.4" /fv "project1:1.0.0.1;project2:1.2.3.4" /fvn "project1:1.0.0.1;project2:1.2.3.4"
| Parameters | Required | Description |
|---|---|---|
|
/f |
Yes |
Specifies the configuration file to be used for compiling and deploying the project. The configuration file (in JSON format) can be directly exported from the PowerBuilder IDE, as described in Building a client/server application with commands. PBAutoBuild250 /f c:\SalesDemo_cloud.json |
|
/deploy |
No |
Deploys the PowerServer/PowerClient project only, instead of compiling and deploying the project. If the project has been compiled before, you can use this parameter to skip compiling the project again. PBAutoBuild250 /f c:\SalesDemo_cloud.json /deploy |
|
/l |
No |
Writes the logging information to the specified file. To use relative path in this parameter, make sure to pass this parameter after the /f parameter, so that the relative path specified in this parameter is relative to the path of the configuration file. |
|
/le |
No |
Writes the error information to the specified file. For example, PBAutoBuild250 /f c:\SalesDemo_cloud.json /l deploy.log /le error.log To use relative path in this parameter, make sure to pass this parameter after the /f parameter, so that the relative path specified in this parameter is relative to the path of the configuration file. In the above example, the log files will be generated under the same path as the configuration file. |
|
/lu |
No |
Writes the unsupported PowerScript features to the specified file. For example, PBAutoBuild250 /f c:\SalesDemo_cloud.json /l deploy.log /le error.log /lu unsupport.log To use relative path in this parameter, make sure to pass this parameter after the /f parameter, so that the relative path specified in this parameter is relative to the path of the configuration file. Note: This parameter only takes effect for the PowerServer project. |
|
/v |
No |
The product version (property displayed for executable). |
|
/fv |
No |
The file version (property displayed for executable). |
|
/vn |
No |
The product version (executable version used by installer). |
|
/fvn |
No |
The file version (executable version used by installer). You can specify for multiple projects at the same time, in this format: "[projectname1]:1.0.0.1;[projectname2]:1.2.3.4". Projects are separated with semicolons (";"). For example, PBAutoBuild250 /f c:\test.json /v "project1:1.0.0.1;project2:1.2.3.4" /vn "project1:1.0.0.1;project2:1.2.3.4" /fv "project1:1.0.0.1;project2:1.2.3.4" /fvn "project1:1.0.0.1;project2:1.2.3.4" If no project name is specified, the version number will be used by all projects. For example, PBAutoBuild250 /f c:\test.json /v "1.0.0.1" The version numbers specified by parameters take precedence over those specified in the build file. |
