...
| Tip | ||
|---|---|---|
| ||
Here is a good place to note that topology, workflows, and project creation is are generally performed once and adjusted as required. Populating new objects in the catalog will happen periodically as you create new files in your SCM. Creating packages, and building and deploying them, is an activity where you will live and breath on a daily basis. |
...
| Tip | ||
|---|---|---|
| ||
The package can be any name or convention that is meaningful to your process. Common approaches are to use a change number from your Change Management System (CMS) or a CEMLI/RICEW identifier if using the Oracle AIM methodology. For this tutorial, we will use a fictional change number - CHG0054692. Selection on the build request form is only used to perform actions against them (e.g. move up/down, remove, etc). All files on the build request form will be included in the package, whether selected or not. Deployment order can be specified by changing the order of the files listed in the request form. You can also search and add additional files, or remove them from the request form. Each file allows selection of a particular SCM revision to extract during the build. If left blank, the HEAD (or latest) revision will be used by default. |
...
This option will take you to the same build request form, but will instead by be empty. You can add files by searching by name/path and adding them to the request.
...
Clicking the gear icon will again launch the build request form with package name pre-filled and the same project files added. Also note that the request form selects the SCM revisions of the previous build. To pick up the latest revisions, we will clear out the revision numbers of the changed files.
...