Summary: This section describes how to prepare and deliver the source code of your PowerBuilder application.
Preparation - source code discovery
Discovery is a process that is actioned during the delivery process CAST will attempt to automatically identify "projects" within your application using a set of predefined rules. Discoverers are currently embedded in CAST AIP:
You should read the relevant documentation for each discoverer (provided in the link above) to understand how the source code will be handled.
Using CAST AIP Console
- Supported in AIP Console v. ≥ 1.17.
- See Application onboarding for more information.
AIP Console expects either a ZIP/archive file or source code located in a folder configured in AIP Console. You should include in the ZIP/source code folder all PowerBuilder source code:
- .PBT
- .PBL
- etc.
CAST highly recommends placing the files in a folder dedicated to PowerBuilder. If you are using a ZIP/archive file, zip the folders in the "temp" folder - but do not zip the "temp" folder itself, nor create any intermediary folders:
D:\temp |-----PowerBuilder |-----OtherTechno1 |-----OtherTechno2
Using legacy CAST Delivery Manager Tool
How do I add a source code package to my delivery
See How do I add a source code package to my delivery.
What you should package?
When creating packages to discover and extract your PowerBuilder application you should create them as listed below:
Package | Package name/type | Mandatory? | Location/path | Notes |
---|---|---|---|---|
1 | Source code | Source code root folder | Use the "Files on your file system" / SVN / TFS options in the CAST Delivery Manager Tool: Click to enlarge |
How do I fine-tune my Version ?
See How do I fine-tune my Version for more information.
How do I deliver the Version for analysis?
See How do I deliver the Version for analysis for more information.
Delivery acceptance
See Validate and Accept the Delivery for more information.