Create the Production Sandbox Packaging Job

The sandbox packaging job generates an extension artifact that's ready to deploy to the Oracle Cloud Applications production instance's sandbox. Configure this job only if you want to deploy the extension to the production instance's sandbox.

To package extension for the sandbox, you'll create a build parameter that accepts the sandbox name when the build runs.

1. In the left navigator, click Builds .
2. Click + Create Job.
3. In the New Job dialog box, in Name, enter a unique name.
4. In Description, enter the job's description.
5. In Template, select the System Default OL7 for Visual Builder template.
6. Click Create.
7. Click Configure .
8. Click the Git tab.
9. From the Add Git list, select Git.
10. In Repository, select the Git repository. In Branch or Tag, select the production branch.
11. Click the Parameters tab.
12. From Add Parameter, select String Parameter.
13. In Name, enter a parameter name. You'll use this name to accept the sandbox's name when this job's build runs.
    Here's an example:

    
    

    
    Description of the illustration vbs_sandbox_parameter.png

    
    
14. (Optional) In Description, enter the parameter’s description. For example: Enter the sandbox name.
15. Click the Steps tab.
16. From Add Step, select Application Extension, and then select Package.
17. By default, the packaging step minifies the application's source code before running the build. If you don't want to minify the source files, deselect the Optimize extension check box.

    Minification is a process to remove the unnecessary characters (such as blank spaces, new lines, and comments) from the source code and reduce the size of the files, making the transfer of files consume less bandwidth and storage.

    Note:

    When you deselect the Optimize extension check box, this warning is displayed: Optimization not selected. Packaging without optimization can cause performance problems, so avoid doing so unless you're debugging or troubleshooting.
18. (Optional) If you want to change the artifact file's name, in Artifact, enter the new name. By default, it is extension.vx.
19. In Extension Version, enter the sandbox parameter name you added in step 13. The name must be in the $<PARAMETER_NAME> or the ${<PARAMETER_NAME>} format.
    Example:

    
    

    
    Description of the illustration build_job_package_sandbox_parameter.png

    
    
20. Click the After Build tab.
21. From Add After Build Action, select Artifact Archiver.
22. In Files to archive, enter extension.vx, the build artifact's name. You can also use wild characters. For example, *.vx.
23. If you want to discard the build's old artifacts, click Settings . In the General tab, select the Discard Old Builds check box and specify the discard options.
24. Click Save.