0 views collected around this technical thread.
Jpom is a simple, low‑intrusion Java‑based platform that provides online project building, automatic deployment, daily operations, and monitoring features, offering node management, SSH terminal, Docker handling, and a one‑click installation process suitable for individuals and small enterprises.
Google's research demonstrates that a machine‑learning model trained on build logs and code snapshots can automatically suggest safe, high‑quality fixes for broken builds, boosting developer productivity by about two percent without introducing detectable security risks.
Learn how to use Maven Archetype to create standardized project skeletons, customize templates, generate and share archetypes, and integrate them into IDEs, streamlining Java project initialization, reducing manual setup errors, and improving development efficiency across teams.
Java developers can quickly establish a Go development environment by installing Homebrew, Go, and the Delve debugger, configuring essential environment variables, choosing an IDE such as GoLand or VS Code, organizing projects with standard cmd/internal layouts, managing dependencies via go.mod, automating builds with a Makefile, and debugging or packaging the resulting binaries.
This article describes a systematic approach to reducing mobile app package size by detecting oversized resources, scanning unused assets, enforcing size checkpoints during development, and integrating automated validation into the CI/CD pipeline, illustrated with tools, workflows, and results.
Setuptools is a Python packaging tool that manages dependencies, bundles source code, installs scripts, and provides command-line utilities, and when combined with Sphinx it can automatically generate project documentation, which can be integrated into the build process via a custom build command in setup.py.
The article shares a developer's practical experience of transitioning from backend to frontend by learning Vue and React, exploring component libraries, tackling layout and styling challenges, and integrating the frontend build into a backend Maven project for a complete gateway console.
Scaling a configuration management team from a small startup to a large enterprise reveals seven key lessons about managing tool costs, customization control, infrastructure scalability, build environment governance, early adoption of third‑party solutions, ensuring traceability with many developers, and continuously evaluating tool costs versus market alternatives.
This guide shows two reliable Maven techniques—using the versions-maven-plugin and a placeholder with the flatten-maven-plugin—to safely update version numbers across dozens of modules without manual errors or risky global replacements.
This article explains how to invoke other Groovy scripts and all Groovy files within a directory from a build.groovy file, providing concrete example code that demonstrates calling a Print method in hello.groovy and using it inside mytools.groovy.
This article details the evolution of JD.com’s HarmonyOS app from a monolithic project to a modular componentized architecture, describing the existing structure, encountered build and resource issues, the Android plugin reference solution, the proposed HarmonyOS componentization scheme, implementation steps, and release packaging.
The AirForce platform unifies component architecture, baseline and release management, and automated packaging for a large Android app, eliminating information silos and cumbersome configuration files by enforcing hierarchical dependencies, tracking component metadata, providing fine‑grained conflict detection, and enabling shuttle releases that streamline coordination, improve traceability, and reduce manual effort.
This article provides a comprehensive walkthrough of how ZuanZuan uses Jenkins together with the custom Beetle platform to automatically generate jobs, configure config.xml, optimize front‑end builds, manage compile packages, and address Sonar scan performance issues, complete with diagrams and script examples.
This article explains Gradle's fundamentals, compares it with Maven, introduces Groovy's abstract syntax tree (AST) concepts, and provides a step‑by‑step demo that parses a Gradle script into an AST, modifies it to inject a dependency, and attempts to write the changes back to the original build file.
This article outlines Baidu's evolution of build practices, presenting a group-level continuous delivery pipeline solution that includes a dual-engine ecosystem—standard plugin engine and non-standard containerized engine—and describes the intelligent build platform that enables dynamic, policy-driven, resource-efficient software delivery.
This article explains why a dedicated frontend build platform is needed, describes its core capabilities such as automated build, pluggable pipelines, audit‑based release, and external plugin exposure, and details the Docker‑in‑Docker architecture, process‑pool design, and sample Node.js code for a scalable CI/CD solution.
This article explains why Android developers need Gradle, describes the structure of a default Android project, details Gradle concepts such as projects, tasks, and the wrapper, and walks through dependency configurations, conflict resolution, and the complete build and packaging pipeline for APK generation.
This article explains how ZheZhe leverages Jenkins as an open‑source, plugin‑rich CI scheduler to classify projects, manage unified build scripts and config files, orchestrate job creation, execution, and cleanup, and scale a mixed Linux/macOS build farm supporting thousands of daily compilations.
This article introduces and compares fourteen widely used Jenkins alternatives—including BuildMaster, Microtica, GitLab, CircleCI, Bamboo, TravisCI, Semaphore, Buddy, Drone.io, GoCD, TeamCity, Buildkite, and Zuul—highlighting their key features, project URLs, and typical use cases for modern CI/CD pipelines.
The article describes Luban, a scalable build management platform that provides generic, extensible packaging, template‑based configuration, automatic and manual trigger mechanisms, result storage, and integrated release capabilities to support continuous delivery of multiple mobile applications within Zhuanzhuan.