OCI DevOps Tools
Enables easy integration with the Oracle Cloud Infrastructure (OCI) DevOps service. The DevOps service can host your source code in the Oracle Cloud and build, then deploy, your projects in hosted CI/CD pipelines.
The extension creates a project in the DevOps service, sets up a source code repository, as well as build and deployment pipelines, enabling you to easily transition from local to cloud-based development and deployment.
Supported Projects and Platforms
Supported project types:
Supported GraalVM versions:
Automatic Proxy resolution in NetBeans Language Server
See below for more info on Proxy setup.
If you are working with a Graal Cloud Native (or Spring Boot) project, the extension will set up build pipelines to build containers for your Java-based application and native executable. The extension will also create deployment pipelines that will deploy these containers to an OKE cluster.
If you have a standard Maven or Gradle project, you can still use this extension to build your JAR files in the cloud on the OCI DevOps service, but as of now deployment pipelines are not created.
For more information, see Graal Cloud Native and OCI DevOps service.
To get started, you will need:
Having done the above, and with a Graal Cloud Native, or a Spring Boot, project, you can can now create an OCI DevOps project.
Create DevOps Project
Once you create a DevOps project, the following build targets now become available from within VS Code:
You can run these build targets, which will run in the Cloud in the OCI DevOps service and not locally, by clicking on the triangle run icon.
Default Pipelines Setup
Once built, the container images can be pulled by clicking on the cloud icon, which provides the command required to pull the containers locally.
The build specification files for each pipeline are stored in .devops/. If you update the build specification file, commit and push the change to the DevOps-hosted repository, the build pipelines will be updated to reflect this change. It should be noted that the build pipelines run on custom sized build runners in order to ensure there is suffcient memory to build all native executables using GraalVM Native Image. These can be customised within the OCI Cloud Console.
OCI Kubernetes deployment with OKE
When the build pipeline succeeds, the container image can be deployed to OKE using Deploy OCI Native Executable Container to OKE
deployment pipeline. When complete, the application can be tested in a browser by selecting the action Open in Browser for Deploy pipeline. This will
set up port forwarding using your local
It will perform kubectl port forwarding from OKE to localhost as indicated by the VSCode status bar.
Project Dependencies Vulnerability Audits
The extension also performs project audits for vulnerabilities in third-party project libraries; supported project types are Maven and Gradle. Project Audits require an OCI account (.oci/config file) and uses OCI ADM Knowledgebase which retrieves data from the nvd.nist.gov database. Just select the Run Project Audit action in the Java Projects panel to check for vulnerabilities in an opened project. If a project contains a vulnerable dependency, it is shown in the PROBLEMS view.
When your project is moved into the DevOps service in the OCI Cloud, it is scanned for vulnerabilities by the Application Dependency Management service. The results of this audit can be displayed within the OCI DevOps Services panel by clicking on the plus icon and selecting Add Knowledge Base from the displayed menu.
Adding more OCI DevOps Services
The OCI DEVOPS SERVICES feature is not limited by the four jobs listed in the previous step. There are many more: You can add an existing build pipeline, a build artifact, a container registry, etc.
When working behind firewall over a proxy then VSCode Proxy has to be set ON. In VSCode Settings set Http: Proxy Support to ON. Subsequently when working without proxy set this OFF.
Many tools used to work on Java projects, such as Maven, Gradle,
Provide Feedback or Seek Help