Skip to content
Snippets Groups Projects
Commit 2b4f84ba authored by Paul Phillips's avatar Paul Phillips
Browse files

Merge branch 'pjp-move-cc' into 'main'

Move Cloud Connector handbook pages to new location

See merge request !12028
parents 98bbf42b 8c119181
No related branches found
No related tags found
Loading
Pipeline #1693185592 passed
Showing
with 8 additions and 8 deletions
......@@ -208,7 +208,7 @@
/content/handbook/engineering/infrastructure/capacity-planning/ @andrewn @gitlab-org/scalability @marin
/content/handbook/engineering/infrastructure/core-platform/ @marin
/content/handbook/engineering/infrastructure/core-platform/data_stores/help.md @alexives @rmar1 @nhxnguyen
/content/handbook/engineering/infrastructure/core-platform/data_stores/cloud-connector/ @pjphillips
/content/handbook/engineering/infrastructure/team/cloud-connector/ @pjphillips
/content/handbook/engineering/infrastructure/core-platform/systems/distribution/ @marin @denisra @plu8
/content/handbook/engineering/infrastructure/emergency-change-processes.md @marin @sabrinafarmer
/content/handbook/engineering/infrastructure/incident-management/ @dawsmith @rnienaber @marin
......
......@@ -15,7 +15,7 @@ toc_hide: true
## Summary
This design doc covers architectural decisions and proposed changes aligned with the team's
[technical vision](/handbook/engineering/infrastructure/core-platform/data_stores/cloud-connector/technical_vision/).
[technical vision](/handbook/engineering/infrastructure/team/cloud-connector/technical_vision/).
Refer to the [official architecture documentation](https://docs.gitlab.com/ee/development/cloud_connector/architecture.html)
for an accurate description of the current status.
......
......@@ -551,7 +551,7 @@ These are the stakeholders:
|-----------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| [Remote Development](/handbook/engineering/development/dev/create/remote-development) | Owns the WebIDE ([maintainers](https://gitlab-org.gitlab.io/gitlab-roulette/?currentProject=gitlab-web-ide&mode=show&hidden=reviewer)) |
| [Editor Extensions](/handbook/engineering/development/dev/create/editor_extensions/) | Maintains the GitLab Workflow VS Code Extension ([maintainers](https://gitlab-org.gitlab.io/gitlab-roulette/?currentProject=gitlab-vscode-extension&mode=show&hidden=reviewer)), [Jetbrains](https://gitlab.com/groups/gitlab-org/-/epics/6349), [Neovim](https://gitlab.com/groups/gitlab-org/-/epics/10739), [Visual Studio](https://gitlab.com/groups/gitlab-org/-/epics/10668) extensions and the [language server](https://gitlab.com/groups/gitlab-org/-/epics/2431). Also contributes with UX improvements for Code Suggestions within GitLab Workflow. |
| [Cloud Connector](/handbook/engineering/infrastructure/core-platform/data_stores/cloud-connector/) (`@mkaeppler`, `@nmilojevic1`) | Supports access to Duo for Self-Managed: Cloud Connector, Unit Primitives |
| [Cloud Connector](/handbook/engineering/infrastructure/team/cloud-connector/) (`@mkaeppler`, `@nmilojevic1`) | Supports access to Duo for Self-Managed: Cloud Connector, Unit Primitives |
| [AI Framework](/handbook/engineering/development/data-science/ai-powered/ai-framework/) | Abstraction Layer / AI Gateway for LLM integration to the application (GitLab Chat, Code Suggestions and other AI capabilities) |
| [AI Framework](/handbook/engineering/development/data-science/ai-powered/ai-framework/) (formerly Model Validation) | Custom feature evaluators, evaluation support, automated evaluation tooling |
| [Global Search](/handbook/engineering/development/dev/foundations/search/) | Abstraction Layer / Vector Storage / Semantic search |
......
......@@ -16,7 +16,7 @@ Core Platform focuses on improving our capabilities and metrics in the following
- [Distribution:Deploy](/handbook/engineering/infrastructure/core-platform/systems/distribution/#distribution-deploy)
- [Geo](/handbook/engineering/infrastructure/core-platform/systems/geo/)
- [Gitaly](/handbook/engineering/infrastructure/core-platform/systems/gitaly/)
- [Cloud Connector](/handbook/engineering/infrastructure/core-platform/data_stores/cloud-connector/)
- [Cloud Connector](/handbook/engineering/infrastructure/team/cloud-connector/)
- [Tenant Scale](/handbook/engineering/infrastructure/core-platform/tenant-scale/)
## All Team Members
......
......@@ -10,4 +10,4 @@ Develop the tooling and frameworks to support the scalability and reliability of
* [Database](/handbook/engineering/infrastructure-platforms/data-access/database-framework/)
* [Database Reliability](/handbook/engineering/infrastructure-platforms/data-access/database-framework-reliability/)
* [Cloud Connector](/handbook/engineering/infrastructure/core-platform/data_stores/cloud-connector/)
* [Cloud Connector](/handbook/engineering/infrastructure/team/cloud-connector/)
......@@ -24,7 +24,7 @@ Once we deployed Puma to our entire web fleet we observed a drop in memory usage
### Project Import and Export improvements
This initially started as a [rapid action](/handbook/engineering/development/#rapid-action-issue) due to failing imports and exports on large projects. For the rapid action we were able to assist in troubleshooting the large projects and identified some areas of improvement going forward. Subsequently, as part of the [10x Initiative](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/4951) we identified some [short term project import/export improvements](https://gitlab.com/groups/gitlab-org/-/epics/1810).
This initially started as a rapid action due to failing imports and exports on large projects. For the rapid action we were able to assist in troubleshooting the large projects and identified some areas of improvement going forward. Subsequently, as part of the [10x Initiative](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/4951) we identified some [short term project import/export improvements](https://gitlab.com/groups/gitlab-org/-/epics/1810).
#### Impact - We fixed large imports, reduced execution time, fewer SQL calls
......
......@@ -6,7 +6,7 @@ title: Cloud Connector Group
Make it easy to build a feature into GitLab across multiple types of deployment.
We have formalized our technical vision in a separate [vision document](/handbook/engineering/infrastructure/core-platform/data_stores/cloud-connector/technical_vision/), a living document that we
We have formalized our technical vision in a separate [vision document](/handbook/engineering/infrastructure/team/cloud-connector/technical_vision/), a living document that we
commit to revisiting at least once a year.
## Mission
......@@ -43,7 +43,7 @@ Where we can we follow the GitLab values and communicate asynchronously. Howeve
## Work
We follow the GitLab [engineering workflow](/handbook/engineering/workflow/) guidelines. To bring an issue to our attention please create an issue in the relevant project, or in the [Cloud Connector team project](https://gitlab.com/gitlab-org/cloud-connector-team/team-tasks/issues/new?issue%5Bassignee_id%5D=&issue%5Bmilestone_id%5D=). Add the `~"group::cloud connector"` label along with any other relevant labels. If it is an urgent issue, please reach out to the Product Manager or Engineering Manager listed in the [Stable Counterparts](/handbook/engineering/infrastructure/core-platform/systems/cloud-connector/#stable-counterparts) section above.
We follow the GitLab [engineering workflow](/handbook/engineering/workflow/) guidelines. To bring an issue to our attention please create an issue in the relevant project, or in the [Cloud Connector team project](https://gitlab.com/gitlab-org/cloud-connector-team/team-tasks/issues/new?issue%5Bassignee_id%5D=&issue%5Bmilestone_id%5D=). Add the `~"group::cloud connector"` label along with any other relevant labels. If it is an urgent issue, please reach out to the Product Manager or Engineering Manager listed in the [Stable Counterparts](/handbook/engineering/infrastructure/team/cloud-connector/#stable-counterparts) section above.
### Planning
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment