Create and Configure Deployment Build Jobs and Pipelines
To deploy extensions to other Oracle Cloud Applications instances, you need to set up or create a packaging job, one or more deploy jobs, and a pipeline. Specifically:
- A packaging job packages the extension and creates a build artifact. Instead of creating new packaging jobs, you can use the
extensionName
-Package job that was created with the project. (If you created this project manually, the package job is called Application-Extension-Package.) This job packages the extension and creates a build artifact from the same branch your team members used to deploy to the primary Oracle Cloud Applications Development instance. Remember, this packaging job is configured to trigger a build on every SCM commit. - Create one deploy job for each Oracle Cloud Applications instance you plant to deploy to. You'll also need a user's credentials who can deploy to each Oracle Cloud Applications instance. To create the job, see Create a Deployment Build Job.
- After you've created deployment jobs, create pipelines to run the package job and deployment jobs in sequence. You can create either of these pipelines:
- A pipeline to deploy the extension to the primary and other Oracle Cloud Applications instances.
Instead of creating a new pipeline, configure the existing
extensionName
-Package and Deploy pipeline to deploy to other instances as well. (If you created this project manually, this pipeline's name is Application-Extension Package and Deploy.) See Configure the Default Pipeline to Deploy to Other Oracle Cloud Applications Instances. Remember, the default pipeline runs automatically when a code change is pushed to themain
branch. After you've configured the pipeline, it deploys the extension to all development and test instances on every SCM commit to themain
branch.After creating this pipeline, you'll have one pipeline in your project that deploys to all DEV and TEST instances.
Here's an example of what this pipeline could look like:
- A pipeline to deploy the extension to other DEV and TEST Oracle Cloud Applications instances manually. See Create and Configure a Pipeline to Deploy to Other Oracle Cloud Applications Instances.
Create this pipeline if you don't want to deploy the extension to other instances on every SCM commit, but only after your team members have validated the extension on the on the primary development instance.
After creating this pipeline, you'll have two pipelines in the project: 1) Your primary pipeline, which deploys to the primary development instance, and 2) this pipeline, which deploys to other DEV and TEST instances.
Here's an example of what these pipelines could look like:
- A pipeline to deploy the extension to the primary and other Oracle Cloud Applications instances.
Create a Deployment Build Job
The deployment job deploys the extension's artifact that was generated in the default packaging job to the Oracle Cloud Application's instance. Before you create the job, make sure you have credentials that VB Studio can use to access the instance.