DevOps-Glue API is a Slim 4βbased integration platform designed to enhance DevOps toolchains for small teams. It provides a unified view, RBAC, and RESTful APIs, with support for multiple mainstream Git platforms and CI-agnostic integration.
π§ A Unified Management Console for Jenkins / GitLab CI / Gitea CI / Custom CI
β Make your distributed Jenkins instances, GitLab CI projects, Gitea CI projects and custom CI manageable, visualizable, and auditable
π Unified Build View: Cross-engine search and aggregation of all build history β no more platform switching
π Unified Log Center: Operation logs, API access logs, and deploy logs
π§ Support LDAP/SSO Login: Easily integrate into the company's internal management system, say goodbye to information silos, and achieve account connectivity
π Custom_Push: Orthogonal push-based CI β pull and push coexist simultaneously. [Use case]β
π Fine-grained RBAC: More flexible access control than native plugins, tailored for team-scale organizations
π Non-invasive Integration: API-only connection with zero changes to existing CI configs β onboard in about 10 minutes
Custom Push CI (Custom_Push) β Your CI pushes β Devops-Glue stores metadata only; orthogonal to pull-based CI, can be enabled simultaneously
Multi-Build Channels β Jenkins + GitLab CI + Gitea CI + Custom_Push, switch or coexist freely
Unified Logs β The Log Center includes operation logs, API access logs, and CD deployment logs β for security and log auditing
Build Records β Pull-based and push-based build records unified into one build log view; see everything at a glance instead of hunting across systems
Multi-Platform Git β GitLab Β· GitHub Β· Gitee Β· Gitea, built in-house or SaaS
Full-Chain Mapping β Job/Pipeline/Actions ID β Git repo β Harbor image tag β CD deployment; codeβbuildβartifact auto-association, forming a complete chain together with the CD service
Security Scan Audit β SAST, secret scanning, dependency vulnerability detection, written back via Commit Status
Role-Based Access (RBAC) β Multi-level custom roles with per-role permissions. Built-in system roles; every other role and its permissions are created by admins in the console, with permission keys and implied rules stored in the database
Unified API β Secure tokens with revocation & deletion and fine-grained scope control, for secure third-party calls such as the CD service
Admin Dashboard β Service monitoring / mapping config / security scan / user management / build modes / build records / log center / API management / system settings
Authoritative Build Artifacts β Obtained via scan-sync write-back in the normal build flow; stale records are safely auto-cleaned; on write-back failures they can be back-filled via log derivation; every build artifact must be verified through the image registry
Zero-Config Startup β SQLite by default, one-click switch to MySQL / MariaDB (recommended)