drone

HỆ THỐNG CI/CD DỰA TRÊN CONTAINER SIÊU TINH GỌN: DRONE CI GIẢI PHÓNG HẠ TẦNG KHỎI SỰ NẶNG NỀ CỦA JENKINS Jenkins là công cụ CI/CD kinh điển nhưng việc phải cài đặt môi trường Java, bảo trì hàng tá plugin cũ kỹ thường xuyên xung đột sau mỗi lần cập nhật, và máy chủ build bị ô nhiễm môi trường (Environment Pollution) giữa các lần chạy khiến việc vận hành Jenkins trở thành một gánh nặng thường trực. Drone CI là nền tảng phân phối và tích hợp liên tục (Continuous Delivery Platform) mã nguồn mở hiện đại, hoạt động dựa trên triết lý cốt lõi: mỗi bước trong pipeline là một container Docker độc lập và sạch sẽ. Tech Stack: Được viết hoàn toàn bằng Golang thuần túy cho hiệu năng cao và mức tiêu thụ tài nguyên siêu nhỏ. Kết nối mượt mà với GitHub, GitLab, Gitea và Bitbucket. Tại sao nên dùng? - Môi trường build hoàn toàn cô lập: Mỗi step trong file .drone.yml được thực thi bên trong một container riêng biệt. Sau khi chạy xong, container bị hủy bỏ hoàn toàn, không để lại bất kỳ rác thải hay xung đột phiên bản nào. - Cấu hình pipeline bằng YAML siêu ngắn gọn: Không cần học các ngôn ngữ kịch bản phức tạp như Groovy của Jenkins; cấu hình pipeline trong Drone cực kỳ trực quan và dễ đọc. - Cài đặt và khởi chạy trong 5 phút: Toàn bộ hệ thống máy chủ và runner được đóng gói trong các image Docker nhẹ nhàng, chỉ cần một VPS 1GB RAM là có thể vận hành mượt mà cho cả team. Dự án sở hữu hơn 32.000 stars trên GitHub và là sự lựa chọn số một cho các đội ngũ công nghệ muốn hiện đại hóa quy trình CI/CD nội bộ. Link tham khảo: harness/drone #OpenSourceVN #VNOSS #opensourcevn #vnoss #DevCommunity #DroneCI #CICD #DevOps #Docker #JenkinsAlternative #Golang

Drone: 4,692 fingerprints against 26,577 titles, and a CI server that already holds your deploy keys Drone: 4,692 fingerprints against 26,577 titles, and a CI server that already holds your deploy keys A continuous integration server is a machine that runs code from your repository with credentials you gave it. Drone is one of the smaller players in that category, and the gap between its two measurement methods is the largest in this batch after Coolify. The measurements On 23 October 2026, ZoomEye returned 4,692 matches for app="Drone", 26,577 matches for title="Drone", and 8,440 matches for title="Drone" && port="80". A title count more than five times the fingerprint count is a strong signal that the string is doing work the product did not ask it to do. "Drone" appears in page titles for hardware, for photography, for music, and for a great many other things. The application fingerprint query is the only one of the three that is plausibly describing the CI product. The port-constrained query is less useful here than in other articles in this batch, because port 80 is the most common port on the internet. Restricting a generic word to a generic port narrows the population without making it specific. Treat 8,440 as a lower bound on coincidence rather than an estimate of CI servers. Why the fingerprint number is the one to use 4,692 is a defensible magnitude for a self-hosted CI tool with a long history and a large open-source following. The figure is small enough to be a real product population and large enough that automated scanning against it is economically rational for an attacker. What a Drone server holds is the reason that matters. A CI server is configured with a source control token that can read repositories, a registry credential that can push images, and usually a deployment credential for one or more target environments. It also holds the environment variables of every pipeline it builds, which in most organisations includes at least one production secret that someone put in a pipeline because it was the fastest path. That combination makes a CI server a higher-value target than a web application of the same size. It is trusted by systems that are not themselves exposed, and it holds the keys to them. The repositories as an attack path A public CI server with an open registration policy is worse than an exposed dashboard. Drone's model links a server to a source control provider, and a user who can authenticate can create a build that runs arbitrary code in the runner. If the runner shares a network with production, or if the pipeline environment contains organisation-wide secrets, that build is a compromise path that requires no vulnerability at all. This is not a defect in Drone. It is the intended behaviour of a CI system, and every product in the category shares it. The control is who can register, which repositories can build, and what secrets a build can read. Reading the counts with discipline State the facts: 4,692 application fingerprint matches, 26,577 title matches, 8,440 title matches restricted to port 80, sub-type all, collected on 23 October 2026. Note explicitly that the title field is a common English word and that the title-based figure should not be used as an install count. None of the three counts reveals a release version. Drone's release history includes security-relevant changes, and the changelog is the authoritative source for what a given version contains. Operational checks Confirm whether your Drone instance allows open sign-up. If it does, the set of people who can run code on your runners is larger than the set of people you have onboarded. Review which secrets are available to a pull request build as opposed to a trusted branch build. A pipeline that exposes deployment credentials to a fork's pull request is a credential leak waiting for a contributor. Restrict the runner network. A runner that can reach the production database because it sits on the same subnet is a design decision that a firewall rule can reverse. Log and review the creation of new builds by users who have not built before. The signal is behavioural and it is available in the product's own audit surface. The closing point The gap between 26,577 and 4,692 is a reminder that a common word in a page title is not a measurement. The number that matters for this product is the smaller one, and the reason it matters is not the server's own interface but the credentials that interface was given. References - Drone documentation, docs.drone.io - Drone project repository, drone/drone - ZoomEye AI query results collected 23 October 2026 for app="Drone", title="Drone", and title="Drone" && port="80", sub-type all

Harness: An end-to-end developer platform with Source Control Management, CI/CD Pipelines, Hosted Developer Environments, and Artifact Registries (38k stars) What it does All text below is quoted directly from the project README. >Harness Open Source is an open source development platform packed with the power of code hosting, automated DevOps pipelines, hosted development environments (Gitspaces), and artifact registries. Overview: - Where Drone focused solely on continuous integration, Harness adds source code hosting, developer environments (gitspaces), and artifact registries; providing teams with an end-to-end, open source DevOps platform. - The goal is for Harness to eventually be at full parity with Drone in terms of pipeline capabilities, allowing users to seamlessly migrate from Drone to Harness. - Harness pipelines run inside Docker containers. - The application automatically negotiates the Docker API version with your Docker daemon, so it works with various Docker versions including Docker Desktop, Rancher Desktop, Colima, and native Docker on Linux. - This project includes a full user interface for interacting with the system. - This project includes a swagger specification. >To install Harness yourself, simply run the command below. Once the container is up, you can visit localhost in your browser. Repository harness/harness Repository stats |Metric|Value| |:-|:-| |Stars|38,650| |Forks|3,433| |Last release|v2.28.2 (2026-04-20)| |Languages|Go 62.4%, TypeScript 33.1%, SCSS 3.1%| |Contributors|84| |AI contributor accounts (Claude / Codex / Cursor / Copilot)|None| |AI co-authored commits|None| Main contributor |Field|Value| |:-|:-| |Name|Marko Gacesa| |GitHub|@marko-gacesa| |Commits to this repo|372 (top contributor)| |Company / Location|Belgrade, Serbia| |Followers|22| |Public repos|7| |On GitHub since|2012-06-18| ────────────────────────────── 📌 How many great GitHub repos have you discovered and completely forgotten about? Don't let another useful tool disappear into your Reddit feed. Get the community's best repos, organized by category, plus key takeaways from real developer discussions, delivered to your inbox twice a week. 📬 Never lose track of great repos again. Subscribe free.

drone: A SuperCLI Plugin Guide drone Continuous integration and delivery platform CLI Source harness/drone Tags - drone - ci-cd - devops - automation Installation 1. brew install drone 2. Verify: drone --version 3. supercli plugins install ./plugins/drone --on-conflict replace --json About SuperCLI This plugin is part of the SuperCLI ecosystem - a unified CLI plugin manager for AI agents and developers. Discover, install, and orchestrate thousands of command-line tools with SuperCLI.

🏆 [GitHub Repo of the Day] harness: The Free Tool Taking Over GitHub! #shorts Discover harness/harness: Harness Open Source is an end-to-end developer platform with Source Control Management, CI/CD Pipelines, Hosted Developer Environments, and Artifact Registries. 💬 Comment "HARNESS" below for the direct link, or grab it from the links below: 👉 Interactive Star History & Live Analysis: githubrepo.cloud ⭐ Embed Live Verified Badges in your README: githubrepo.cloud 🔗 Direct GitHub Repository: harness/harness 📊 Repository Specs: ⭐ Stars: 38,479 🍴 Forks: 3,411 💻 Language: Go 📜 License: Apache-2.0 #shorts #harness #buildautomation #buildpipelines #ci #cicd #linux #devops #commandline