Glossary
Before using the release repos and self-hosted repos of CodeArts Artifact, review the basic concepts.
Package
A package is a collection of source code files or build products. It groups related components that are distributed together to provide specific functionality. Packages are typically stored in binary or compressed formats. Managing packages and their metadata is the foundation of release management.
Release Repos
A release repo is a general-purpose artifact repository that stores and manages artifacts in various formats. In addition to basic storage functions, it also supports important functions such as build and deployment tool integration, version control, and access control. It provides a standardized way for enterprises to manage all artifact types generated during software development.
Self-Hosted Repos
A self-hosted repo manages private packages (often called private repositories). It provides a unified way to manage packages generated during software development. Different programming languages use different package formats. Developers often need to share packages with their team during development. Self-hosted repos serve as a central place where these packages can be stored and accessed by others, making it easy for team members to obtain packages from repositories. This enables secure management and sharing of packages within an organization.
Local Repository
A local repository is a type of self-hosted repos. It is a physical repository where artifacts are fully hosted on the CodeArts Artifact server. You can upload various artifact types to a local repository to store and manage your build outputs, dependencies, and third-party artifacts.
- Privacy: The repository is fully controlled by you and is not shared with external systems.
- Durability: Data is permanently stored on the CodeArts Artifact server.
- Performance: Fast access speeds.
- Usage: It is suitable for storing self-developed components, binary files, and configuration files.
Virtual Repository
A virtual repository is a type of self-hosted repos. You can configure proxy sources in a virtual repository to connect to local third-party repositories. It also offers local repository functions and provides a unified entry to make setup easier for you.
- Aggregation: A virtual repository can include multiple local repositories.
- Single URL: Resources in multiple repositories can be accessed through a single logical URL.
- Transparency: Clients do not need to know which repository stores the resources.
- Flexibility: Repositories can be added or removed as needed.
- Usage: It is used to simplify dependency management and build processes, and provides a unified view.
Project Object Model
A project object model (POM) is the basic unit of work in a Maven project. It is an XML file that defines project configuration, build instructions, and dependencies. It also manages project metadata, including source code structure, configuration files, developer and organization information, access permissions, project URLs, and dependencies. When a build task is run, Maven searches for the POM in the current directory, reads its content, obtains the required configuration information, and builds the target package.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot