The Oracle Analytics Cloud plugin provides operations to manage the build and deployment of WebCatalog objects across your cloud instances.

Supported Versions

Key Features

Source WebCatalog from SCM or Development environment.
Supports FlexDeploy Full as well as Package-Based for WebCatalog objects.
- Package-project option allows users to select various catalog objects (via FlexDeploy package) for build and deployment. Change detection and reporting are maintained for each individual object.
- Package-project option can leverage dynamic packages for an effective way to manage consistent deployments at the folder level.
When sourcing from OAC development instance, files are populated with an extension mapping to its type.
Folders are automatically deployed first without children, followed by their components
Operations to support synching WebCatalog objects to a source code repository.
Allows backing up catalog items before deployment, ensuring a smooth rollback if necessary. See Build & Deploy Projects for details on performing deployment rollback.

Package-based projects are created using the "Oracle Analytics Cloud" project type.

WebCatalog objects can be sourced either from the Backend (Oracle Analytics Cloud development instance) or from a supported SCM (Source Control Management) system.
If you want to source directly from your development environment and deploy to other environments, select "None" for SCM Type. Artifacts will still be captured at build time in the FlexDeploy repository, enabling reproducible deployments.
To source from an SCM repository, specify the SCM Type and repository details, then perform a Discover from SCM on the File Catalog. For example, when using Git, configure the Git repository instance and set up a Sparse checkout folder if necessary. Ensure that the directory structure of the WebCatalog objects under the sparse checkout folder mirrors the OAC WebCatalog Catalog path in Oracle Analytics Cloud.
In Package-Based deployment mode, folder deployment only deploys the folder itself and not its child objects. You can select specific child objects to include in the deployment package.
OAC project packages use a "stop on failure" deployment method. This means that if any file in the package fails, subsequent files will not be deployed. This method helps avoid a cascade of failures if the deployment of the parent folder fails.