What Project Artifacts Are Created?
When you create a new project, several other VB Studio artifacts are also created for you. VB Studio shows you a status diagram so you can follow along as each artifact is generated:
![Description of projprogress.png follows Description of projprogress.png follows](img/projprogress.png)
These artifacts include:
- A Git repository, which will contain the source code for all the extensions based on this project.
To see the Git repository's files, go to the Project Home page, click the Repositories tab, then click the Git repository name:
- A Development environment,
pointing to the development instance where the Oracle Cloud Application you plan to
customize is running. (A VB Studio environment can include one or more
instances of Oracle Cloud Applications, Visual Builder, Oracle Cloud SaaS, or Oracle
Cloud Infrastructure service instances, so you can treat them as a single entity.)
To see the definition for the Development environment, click
Environments in the VB Studio navigator:
- A workspace, which is a private area where you work on your extensions. Each user has a unique workspace, although users can collaborate on the same extension by cloning each other's workspace (which also clones the project's Git repository).
- Build jobs that package and deploy the extension's artifact to Oracle Cloud Application's development instance.
The package job, named extensionName-Package, generates the extension's artifact file. The deploy job, extensionName-Deploy, deploys the extension's artifact file to the Oracle Cloud Application instance defined in the Development environment. (If you create a project manually, these jobs are named Application-Extension-Package and Application-Extension-Deploy.)
- The extensionName-Package and Deploy pipeline, which runs the package and deploy build jobs in a sequence. (If you create a project manually, this pipeline is named Application Extension - Package and Deploy.)
- A VM executor, but only if this is the first project in this VB Studio's instance and this instance did not already have any VM executors. (Builds in a build system run in build executors. The operating system and software packages required to run builds on build executors are defined in build templates.) The VM executor uses the System Default OL7 for Visual Builder executor template. You can use this VM executor to run build jobs that reference the System Default OL7 for Visual Builder template in the current project and other projects as well.