At the completion of this section, you will:
...
The left pane is project explorer and provides the ability to create folders, applications and projects. Folders are used for organization structure and there is no limit to the number of folders created. An application is a special folder and there is only one allowed at the lowest level of the folder structure. Projects can only be created under an application. It is a best practice to name Application with same name as name of JDeveloper application. Right clicking on a folder or an application will provide a menu for creation.
...
- Build Workflow (BuildConfigs)
- Deploy Workflow (DeployConfigs)
- Build Instance (SOA)
- Deploy instance (SOA)
- SCM type (GIT)
- GIT Instance (GITREPO)
Sparse Checkout Folder Script ("WLSConfigurations/HumanResources")
- Checkout Folder Script is a subfolder where the sources will be checked out to. We don't need a subfolder, so delete the input
- Stream Name (master)
| Tip |
|---|
The properties files will be pulled from Git after the repository, defined by the GITREPO instance, is cloned locally. The Branch Name Script defines the branch to utilize within the repository and the Sparse Checkout Folder provides the path to the files. |
...
The SCM Configuration script entry fields (Branch Name, Tag Name, Sparse Checkout Folders and Checkout Folder) are Groovy script enabled to provide increased flexibility. The double quotes on the Sparse Checkout Folders Script indicate a literal to the Groovy script and will not be replaced. The drop down to the right of the entry field provides the available variables that can be utilized in the Groovy script, which will be replaced with actual values on execution.
...