feat: Add native integration for OneDev DevOps Platform
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 5/5
- Tempo estimado
- Mais de uma semana
- Facilidade para iniciantes
- 15/100
Direção de pesquisa
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.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
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.
- Linguagem predominante
- Go
- Estrelas
- 421
- Forks
- 50
- Merge médio
- 17h 34min
- PRs com merge (30d)
- 80
Preparar o ambiente
- Inclui um Dockerfile ou arquivo Docker Compose
- Sem modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de Windshiftapp/core
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 66/100
Windshiftapp/core#542 ·
Mantenedores costumam responder em até 1 dia
-
Time Tracking FilteringAberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 64/100
Windshiftapp/core#334 · 2 comentários ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
Windshiftapp/core#259 · 1 comentário · 1 reação ·
Mantenedores costumam responder em até 1 dia
-
[Bug][AI chat] Select menu dont appear when on index pageTalvez já em andamento @valentimarco assumiu hoje. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 20/100
Windshiftapp/core#541 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 3/5 1-2 dias Facilidade para iniciantes 45/100
Windshiftapp/core#538 · 1 reação ·
Mantenedores costumam responder em até 1 dia
Todas as issues de Windshiftapp/core
Issues semelhantes
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
karmada-io/karmada#8101 ·
Mantenedores costumam responder em até 1 dia
-
product:platform
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 77/100
Infisical/infisical#9746 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
CrossEntropyFilter raises on zero probabilities and single-class resultsTalvez já em andamento @NopeCharon assumiu hoje. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
Mantenedores costumam responder em até 1 dia
-
bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 86/100
txn2/mcp-data-platform#2728 ·
Mantenedores costumam responder em até 1 dia
-
effort:s impact:low raised-by:worker risk:low
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 70/100
medici-finance/assay#7259 · 1 comentário ·
Mantenedores costumam responder em até 1 dia