El contenido no se encuentra disponible en el idioma seleccionado. Estamos trabajando continuamente para agregar más idiomas. Gracias por su apoyo.
- What's New
- Function Overview
- Product Bulletin
- Service Overview
- Getting Started
-
User Guide
- Process of CodeArts Repo
- Purchasing CodeArts
- Accessing CodeArts Repo Homepage
- Environment and Personal Settings
- Migrating Code and Syncing a Repository
- Creating a Repository
- Viewing Activities
- Viewing Repository Statistics
- Configuring Repository Settings
- Hierarchical Repository Management
- Configuring a Repository
- Managing Repo Member Permissions
- Cloning or Downloading Code Repo to a Local PC
- Uploading Code Files to CodeArts Repo
- Developing a Workflow
- Creating and Configuring a CodeArts Project
- Committing Code to CodeArts Repo and Creating a Merge Request
- Managing Merge Requests
- Managing Code Files
- Security Management
- Best Practices
-
FAQs
- Authentication
- Member Permissions
-
Uploading and Downloading Code
- "Error: Deny by project hooks setting 'default': message of commit" Is Reported When Code Repository Is Pushed from the Local Host to CodeArts Repo
- Pushing Binary Files to CodeArts Repo Failed
- Error "'origin' does not appear to be a git repository..." Is Reported When the Git Push Command Is Executed
- Error "The requested URL returned error: 401" Is Reported When HTTPS Is Used to Clone Code in CentOS
- Error "Merge branch 'master' of https://test.com Please Enter a commit" Is Reported When Pulling Code Using the Git Pull Command
- Message "fatal: refusing to merge unrelated histories" Is Displayed
- How Do I Prevent Files Containing Secrets from Being Pushed to CodeArts Repo?
- Migrating Repositories
- Merge Request
- Fork Sync
- Repository Capacity
- FAQs
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
APIs
- SSH Key
-
Repository
- Obtaining Files in a Branch Directory
- Obtaining Repository Statistics
- Obtaining Image Files of a Specific Branch in a Repository
- Modifying the Status of a Repository Referenced by a Pipeline
- Checking Whether a User Has the Repository Administrator Permission
- Setting a Repository to Public or Private
- Obtaining the Content of a Specified File in a Specified Branch of a Repository
- Obtaining a Public Template List
- Creating a Repository
- Obtaining a Repository Short ID to Generate the Details Page URL
- Querying a Commit of a Branch by Repository or Repository Group Name
- Querying Branches of a Specified Repository
- Querying a Commit of a Repository Branch by the Repository ID
- Adding a Deploy Key
- Deleting a Deploy Key
- Obtaining the Last Commit Statistics of a Repository
- Repository Statistics
- Deleting a Repository
- Viewing a Repository Creation Status
- Querying the Tag List of a Repository
- Adding a Tag
- Querying Details About a Repository
- Obtaining the number of committed code lines
- Downloading a Repository
- Creating a Protected Branch
- Deleting a Protected Branch
- Deleting Protected Branches in Batches
- Creating a Protected Tag
- Deleting a Protected Tag
- Obtaining a Repository Branch List
- Obtaining the MR List of a Repository
- Obtaining MR Details of a Repository
- Obtaining the Repository IP Address Whitelist
- Adding the Repository IP Address Whitelist
- Modifying the Repository IP Address Whitelist
- Deleting the Repository IP Address Whitelist
- Obtaining the Changes of an MR
- Associating a Repository with a Member Group
- Locking a Repository Based on the Repository Short ID
- Unlocking a Repository Based on the Repository Short ID
- Approving an MR
- Obtaining Associated Work Item Information
- Obtaining Reviewer Information Based on the Repo Short ID and Merge Request Short ID
- Obtaining the List of Changed Files
- Tenant
- Group
- Project (V2)
- RepoMember
- Commit
- File
- User
- Webhook
- Project
- Repository Management (V2)
- Review
- Application Examples
- Appendix
- Videos
- General Reference
Show all
Copied.
Data Protection Technologies
CodeArts Repo uses multiple methods to secure data.
Method |
Description |
Reference |
---|---|---|
Transmission encryption (HTTPS) |
A code repository hosted in CodeArts Repo is flushed to disks on the cloud to prevent people other than the data owner from accessing users' plaintext data and prevent data leakage on the cloud. The code encryption process is transparent to users. Users can use any official Git client to access the code repository on CodeArts Repo. |
- |
Key management |
SSH key and deployment key management ensures that the request is initiated by the request initiator so that users can only browse authorized data, securing data. |
For details about the SSH key pair and how to obtain it, see SSH Key. |
git-crypt encrypted transmission and storage |
git-crypt is a third-party open-source software that can transparently encrypt and decrypt files in the Git repository. |
It can encrypt and store specified files and file types. Developers can store encrypted files (such as confidential information or sensitive data) and shared code in the same repository and pull and push them like in a common repository. Only the person who has the corresponding file key can view the content of the encrypted files, but others are not restricted to read and write unencrypted files. For details about encrypted transmission and storage using git-crypt and how to obtain git-crypt, see About git-crypt. |
Sensitive data anonymization and high-value data encryption |
CodeArts Repo uses unified and accurate data to support applications and services for data security and privacy. |
Logs and databases contain sensitive data, including but not limited to keys and account information. To prevent security issues caused by sensitive data leakage, the data is anonymized or encrypted by CodeArts Repo. The principle is a hash function, which generates a digest for a piece of information to prevent tampering. |
Anti-DDoS tool |
Advanced Anti-DDoS (AAD) is a tool for defending against DDoS attacks. AAD can protect your servers against large volumetric DDoS attacks so your Internet services can keep being available. |
AAD supports two traffic diversion modes: DNS resolution and IP address directing to protect website domain names and service ports. Based on the forwarding rules you configure for your services in AAD, AAD directs the DNS domain name resolution or service IP address to the AAD instance IP address or CNAME address for traffic diversion. Access traffic from the public network preferentially passes through an AAD equipment room. Malicious attack traffic is cleaned and filtered in the AAD traffic cleaning center. Normal access traffic is returned to the origin server through port protocol forwarding, ensuring stable access to the origin server. |
Traffic limiting |
Traffic limiting can be used to limit the number of HTTP requests sent by a user within a specified period of time. Traffic limiting is used to protect upstream application servers from being overwhelmed by too many concurrent user requests. |
CodeArts Repo mainly uses Nginx and APIGW flow controls. Nginx uses the leaky bucket algorithm to limit traffic. This algorithm is widely used in communication and packet switched computer networks to handle bursts when bandwidth is limited. APIGW flow control limits the number of times an API is called within a specified period to protect backend services and provide continuous and stable services. |
Backup & DR |
Backup and DR not only prevent data loss, but also ensure that services on the server are taken over after the server breaks down to ensure service continuity. This feature ensures that users can continuously use application services, service requests of users can run continuously, and services provided by the information system are complete, reliable, and consistent. |
- |
Hash-based shard storage |
Hash-based sharded storage improves confidentiality and privacy. Data sets are divided into independent and orthogonal data subsets based on certain rules. Then, the data is randomly distributed to multiple nodes. No node can access the complete data. They contain only a part of the data. |
- |
Watermark |
To prevent unauthorized photos, screenshots, or other means from spreading core assets, you can enable watermark settings. |
For details about how to set watermarks, see Watermarks. |
Backup |
The repository backup operation secures code and prevents others from deleting code by mistake. There are two backup modes:
|
For details about how to back up the repository, see Repository Backup. |
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