Git source code management for Oracle Integration Artifacts using VB Studio
Overview
Oracle Visual Builder Studio (VB Studio) is a powerful application development platform that enables your team to organize and manage their work successfully at all phases of the app development lifecycle. VB Studio can also be linked to source control (Git) so that developers can keep track of changes, apply version control best practices, and collaborate with their teammates to develop applications.
Oracle Integration Cloud Service is a lightweight integration solution for connecting cloud-based applications. It connects both your cloud application and your on-premise application, making connectivity between both easier.
In this post, you’ll learn how to use VB Studio’s CI/CD capabilities to configure build jobs that export Integration artifacts from Oracle Integration instance and push it to VB Studio’s Git repository.
The Setup
Export Integration Artifact and push to Git
Step 1: Create New Project
To create a new project, go to the Organization tab in VB Studio and click Create.
Create a new project by entering the Project Name and selecting ‘Initial Repository’ as the template.
Step 2: Add Service Instances
Click on Environments tab and add the Oracle Integration instance you want to export the integration from.
To do this, go to Create Environment > Add Instance. Select ‘Visual Builder’ as the instance type and ‘Identity Domain’ as the authentication method. Select the Integration instance and click ‘Add’.
Step 3: Configure a Build Job to export the integration artifact
Go to Builds and click on ‘Create Job’ to create a new job.
Enter the Job Name. Select the System Default OL7 template for Visual Builder as the template and click create.
In the Job Configuration, configure Git by selecting the Git repository.
Under Steps, use the Oracle Integration > Export Integration step to export an Integration artifact from an Oracle Integration instance.
To do so, go to Steps > Add Step and pick Oracle Integration > Export Integration.
Enter the Instance, Username/Password, Identifier and the Version.
For more details on how to configure a build job that exports an Integration artifact from an Oracle Integration instance, refer this link.
The above build step will generate an .iar file which can be pushed to Git for version control.
Step 4: Configure a Build Job to add and commit the exported file to Git
The .iar file generated in the previous step is a binary file. Since Git cannot track a binary file, we will unzip it first and then push it to Git.
To do this, add a new build step by clicking Add Step > Common Build Tools > Unix Shell and enter the commands as shown below.
The above commands will unzip the .iar file, add the files to the Git staging area and commit it.
Step 5: Publish the Artifacts to the Git repository
Go to After Build Tab and Add ‘Git Publisher’ after build action.
To push Git artifacts to the Git repository only if the build succeeds, select the Publish only if build succeeds check box.
To push merges back to the target remote name, select the Merge results check box.
Enter the branch to push to remote repository.
Click Save.
For more details of Git Publisher, refer to this link.
Step 6: Run the build job
Not bad! Want to share your experience? Join us on our public Slack.
You can also sign up for our Free Tier and try it out.
