feat: Add native integration for OneDev DevOps Platform

Đang mở
#376 1 bình luận 1 reaction 0 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 1 ngày

Chưa có ai nhận issue này.

Đánh giá

Độ khó
5/5
Thời gian dự kiến
Hơn một tuần
Mức phù hợp với người mới
15/100
Loại issue
Tính năng
Độ rõ ràng
Khá rõ ràng
Mức độ hoạt động
Sôi nổi
Công nghệ
go
Lĩnh vực
api, backend

Hướng nghiên cứu

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.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

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 ws CLI 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 OneDevProvider configuration block to the integration settings.
  • Required inputs: Instance URL, Token / OAuth Credentials, and Organization/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 ➡️ OneDev Open state.
  • Windshift In Progress ➡️ OneDev In Progress state.
  • Windshift Done ➡️ OneDev Closed state.
B. User & Identity Resolution
  • Map Windshift.User.Email or Windshift.User.Username to OneDev.User.Name to 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.local connectivity).

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.
Ngôn ngữ chính
Go
Star
421
Fork
50
Merge trung bình
17 giờ 34 phút
Pull request đã merge (30 ngày)
80

Chuẩn bị môi trường

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của Windshiftapp/core

Tất cả issue của Windshiftapp/core

Issue tương tự

Thêm issue về Go

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.