feat: Add native integration for OneDev DevOps Platform
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 15/100
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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.
- Lingua principale
- Go
- Stelle
- 421
- Fork
- 50
- Merge medio
- 17h 34m
- PR unite (30g)
- 80
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di Windshiftapp/core
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
Windshiftapp/core#542 ·
I maintainer di solito rispondono entro 1 giorno
-
Time Tracking FilteringAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 64/100
Windshiftapp/core#334 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
Windshiftapp/core#259 · 1 commento · 1 reazione ·
I maintainer di solito rispondono entro 1 giorno
-
[Bug][AI chat] Select menu dont appear when on index pageForse già presa @valentimarco l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 20/100
Windshiftapp/core#541 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 45/100
Windshiftapp/core#538 · 1 reazione ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di Windshiftapp/core
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
karmada-io/karmada#8101 ·
I maintainer di solito rispondono entro 1 giorno
-
product:platform
Difficoltà 2/5 1-3 ore Idoneità per principianti 77/100
Infisical/infisical#9746 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
CrossEntropyFilter raises on zero probabilities and single-class resultsForse già presa @NopeCharon l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 86/100
txn2/mcp-data-platform#2728 ·
I maintainer di solito rispondono entro 1 giorno
-
effort:s impact:low raised-by:worker risk:low
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
medici-finance/assay#7259 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno