...
- Enter the SCM type for your project
- Select the build workflow that was created for EBS
- Select the build instance on which to run the builds. If you are planning to build AOL objects from your development EBS instance, this instance must map to that EBS instance. If you are planning to source all objects from an SCM only then this instance need not be an EBS instance.
- Select the deploy workflow that was created for EBS
- Select your target EBS instance(s)
- Select the SCM instance containing the EBS customizations for this project
- Enter the required attributes for your SCM source code. Additional information on the SCM configuration is available in the FlexDeploy User's Guide.
Click Save to save your changes.
...
Note: You can choose to restrict these configurations to an Apps DBA group (or other) if desired. Review the Security section of the FlexDeploy User's Guide for more information.
Click on the Project Files tab. Select the SCM stream to retrieve the files from, and click the Populate from SCM button. All customization files will be retrieved from the SCM, and their metadata will be auto-discovered/defaulted.
Info |
---|
If using ForĀ Git, make sure that the Git executable (version must be installed on FlexDeploy server and it must be accessible in its PATH. The Git executable version must be 1.7.9 +) is installed and in the Path of the FlexDeploy serveror higher. |
When populating for the first time it can take up to few minutes, depending on the number of files you are managing. After completion you will see the files as shown below.
...