This commit is contained in:
2026-06-03 17:17:46 +00:00
parent 540a3cd8d2
commit 8d3b2d53e8
+47
View File
@@ -0,0 +1,47 @@
# Repository gitjet/gitjet.ru
## Delivery overview
This repository provides a comprehensive documentation and AI-driven summary for the GitJet platform, which is an open-source project that aims to revolutionize the way developers collaborate on software projects. The repository includes various technical files such as `README.md`, `.docs/technical.md`, and others related to the project's architecture, development process, and documentation.
## CI pipelines
The GitJet platform uses GitHub Actions for continuous integration (CI) and deployment (CD). The following are the main CI/CD pipelines:
1. **Build and Test Pipeline:** This pipeline is triggered whenever a pull request or push event occurs in the repository. It builds the project using Docker, runs unit tests, and generates code coverage reports.
2. **Deployment Pipeline:** this pipeline is triggered when a new tag is pushed to the repository. It deploys the built artifacts to the specified environment (e.g., staging or production).
## CD and release
The GitJet platform uses Helm for managing Kubernetes deployments. The following are the main components:
1. **Helm Chart:** the `gitjet/gitjet-helm` chart is used to deploy the GitJet platform on a Kubernetes cluster.
2. **Image Tags:** The images used by the deployment pipeline are tagged with the commit hash and version number.
3. **Environments:** The GitJet platform has two environments: staging and production.
## Workflows and automation
The `gitjet/gitjet-workflows` repository contains various workflows for managing the GitJet platform. These include:
1. **Release Workflow:** this workflow is triggered when a new tag is pushed to the repository. It creates a release, builds the artifacts, and deploys them to the specified environment.
2. **Deployment Workflow:** This workflow is triggered whenever a pull request or push event occurs in the repository. It deploys the built artifacts to the specified environment (e.g., staging or production).
## Infrastructure dependencies
The GitJet platform uses various infrastructure components:
1. **Registries:** The `gitjet/gitjet-registry` registry is used to store Docker images for the GitJet platform.
2. **Clusters:** The `gitjet/gitjet-cluster` cluster is used to deploy the GitJet platform on a Kubernetes cluster.
3. **Secrets Managers:** The `gitjet/gitjet-secrets` secrets manager is used to store sensitive information such as API keys, database credentials, and other confidential data.
## Runbook hooks
The `gitjet/gitjet-runbooks` repository contains various runbook hooks for managing the GitJet platform. These include:
1. **Health Checks:** This hook checks the health of the GitJet platform by verifying its availability and performance.
2. **Migrations:** this hook performs database migrations to keep the database schema up-to-date with the latest changes in the codebase.
3. **Rollback Hints:** this hook provides rollback hints for any issues that may arise during deployment or maintenance.
## Repository summary
The `gitjet/gitjet.ru` repository is a comprehensive documentation and AI-driven summary of the GitJet platform, which is an open-source project that aims to revolutionize the way developers collaborate on software projects. The repository includes various technical files such as `README.md`, `.docs/technical.md`, and others related to the project's architecture, development process, and documentation. The GitJet platform uses GitHub Actions for continuous integration (CI) and deployment (CD), Helm for managing Kubernetes deployments, and various infrastructure components such as registries, clusters, and secrets managers.