feat: Add native integration for OneDev DevOps Platform
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 15/100
Línea de trabajo
The payload names no source files or tests, so start by finding the existing Gitea/Forgejo provider code in the repo and the integration settings screen. The issue's example webhook JSON and the POST /api/repositories/{repositoryId}/commits/{commitHash}/statuses endpoint are the concrete contracts to check against. Done would mean a maintainer-agreed design for auth (PAT vs OAuth), state mapping and webhook registration. This is design work, so confirm scope with maintainers before coding.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Feature Request: Add native integration for OneDev DevOps Platform
Is your feature request related to a problem? Please describe.
Currently, users hosting their source code and CI/CD pipelines on OneDev cannot seamlessly connect their repositories to Windshift. While Gitea and Forgejo enjoy native, out-of-the-box support, OneDev users are forced to rely on complex custom webhooks and REST API workarounds to sync workspaces and trigger automations.
Describe the solution you'd like
We need a native provider integration for OneDev within the Windshift ecosystem. This should include:
- OAuth2 / Personal Access Token Authentication: Easy account linking via OneDev Personal Access Tokens (PAT) or OAuth applications.
- Repository Syncing: The ability to import and track projects directly from a self-hosted OneDev instance.
- Webhook Automation: Automatic registration of webhooks in OneDev to listen for code pushes, pull requests, and issue updates.
- Windshift CLI (
ws) Support: Commands to list, link, and trigger OneDev-backed workspaces natively.
Describe alternatives you've considered
- Managing custom automation via
wsCLI scripts embedded in OneDev CI/CD pipeline steps. - Manually configuring generic inbound webhooks in Windshift, which lacks bidirectional sync and deep repo visibility.
Implementation Details & Requirements
1. Authentication & Connection Layer
- Add a
OneDevProviderconfiguration block to the integration settings. - Required inputs:
Instance URL,Token / OAuth Credentials, andOrganization/User Namespace.
2. Specific Data & Field Mapping
To ensure smooth translation between Windshift objects and OneDev's flexible domain model, the following core schemas must be mapped:
A. State & Status Mapping
Windshift task states must map cleanly to OneDev issue states. Because OneDev allows custom workflows, the integration must default to standard transitions while allowing user overrides:
- Windshift
Backlog/Todo➡️ OneDevOpenstate. - Windshift
In Progress➡️ OneDevIn Progressstate. - Windshift
Done➡️ OneDevClosedstate.
B. User & Identity Resolution
- Map
Windshift.User.EmailorWindshift.User.UsernametoOneDev.User.Nameto correctly handle automated workload assignments and track commit attributions inside workspaces.
3. API Payload & Event Structures
Utilize OneDev's structural REST API to handle lifecycle events. The payload processing engine should support the following specifications:
A. Inbound Webhook Handling (OneDev to Windshift)
The integration endpoint must listen for OneDev event payloads (typically structured around OneDev.Issue or OneDev.PullRequest objects) to trigger workspace syncs:
{
"event": "issue_opened",
"issue": {
"id": 1024,
"number": 42,
"title": "Implement feature X",
"description": "Detailed requirement text...",
"state": "Open",
"submitter": {
"name": "developer_username"
}
},
"repository": {
"id": 56,
"name": "project-repo"
}
}
B. Outbound Status Delivery (Windshift to OneDev)
To reflect Windshift workspace builds and check statuses directly inside the OneDev UI, the provider must send standard status updates to the OneDev commit tracking endpoint:
- Endpoint:
POST /api/repositories/{repositoryId}/commits/{commitHash}/statuses - Payload Structure:
{
"context": "Windshift Workspace Build",
"state": "SUCCESSFUL",
"description": "Windshift environment provisioned successfully.",
"targetUrl": "https://windshift.local"
}
(Valid OneDev states to map: PENDING, RUNNING, SUCCESSFUL, FAILED)
4. User Interface (UI) Components
- Add the OneDev logo to the "Connect a Git Provider" screen alongside GitHub, GitLab, and Gitea.
- Provide clear validation states for self-hosted URLs (e.g., verifying
https://onedev.localconnectivity).
Additional Context
- OneDev Project Home: https://github.com/theonedev/onedev
- This will bridge the gap for users who prefer OneDev's heavy emphasis on built-in Kubernetes CI/CD pipelines over lighter alternatives like Gitea.
- Lenguaje dominante
- Go
- Estrellas
- 421
- Forks
- 50
- Merge medio
- 17 h 34 min
- PR fusionados (30 d)
- 80
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de Windshiftapp/core
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
Windshiftapp/core#542 ·
Los mantenedores suelen responder en 1 día
-
Time Tracking FilteringAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
Windshiftapp/core#334 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Windshiftapp/core#259 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
[Bug][AI chat] Select menu dont appear when on index pagePosiblemente ocupada @valentimarco la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 20/100
Windshiftapp/core#541 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
Windshiftapp/core#538 · 1 reacción ·
Los mantenedores suelen responder en 1 día
Todos los issues de Windshiftapp/core
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
karmada-io/karmada#8101 ·
Los mantenedores suelen responder en 1 día
-
product:platform
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
Infisical/infisical#9746 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
CrossEntropyFilter raises on zero probabilities and single-class resultsPosiblemente ocupada @NopeCharon la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
txn2/mcp-data-platform#2728 ·
Los mantenedores suelen responder en 1 día
-
effort:s impact:low raised-by:worker risk:low
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
medici-finance/assay#7259 · 1 comentario ·
Los mantenedores suelen responder en 1 día