Eliminating the Install Step: A Practical Look at Yarn Zero-Installs
Stop waiting for 'yarn install'. Learn how Yarn Plug'n'Play and Zero-Installs eliminate node_modules to accelerate CI/CD and ensure deterministic environments.
Loading…
ReadMeFeed / Community knowledge
#cicd
Real questions. Useful conversations. Find the people who know your stack.
yarnImplementing Remote Caching in Turborepo for Distributed CI/CD
Learn how to implement Remote Caching in Turborepo to eliminate redundant builds across CI/CD pipelines and distributed development teams.
turboStopping the Bleeding: Using Qodana Baselines to Manage Technical Debt
Stop fighting thousands of legacy warnings. Learn how to use Qodana baselines to ignore existing technical debt and enforce quality gates only on new code changes.
qodanaStopping Pipeline Bloat: Implementing Jenkins Shared Libraries
Stop copy-pasting CI/CD logic across repositories. Learn how to use Jenkins Pipeline Shared Libraries to standardize build patterns and reduce Jenkinsfile bloat.
groovyAutomating Recurring Tasks with GitLab CI/CD Pipeline Schedules
Learn how to implement GitLab CI/CD Pipeline Schedules to automate recurring tasks using Cron syntax and conditional rules to optimize runner usage.
gitlabPreventing Code Decay with Qodana Quality Gates
Stop the 'slow leak' of technical debt. Learn how to use Qodana Quality Gates to prevent code regressions by comparing CI analysis against a stable baseline.
Centralising Jenkins Pipelines with Shared Libraries: A Practical Guide
Tired of copy-and-pasting pipeline code across projects? Learn how Jenkins Shared Libraries let you keep reusable logic in one place, version it, and keep your jobs lean.
jenkinsJUnit 5 Parameterized Tests and CI/CD Report Integration
Managing Test Output Volume When utilizing @ParameterizedTest in JUnit 5 (Jupiter), a single test method may execute hundreds of iterations. While the name attribute allows for descriptive identifiers, the resulting volume of successful iterations can create significant noise within CI/CD logs and XML reporting artifacts. The goal is to maintain a high level
junitQodana baseline merging during concurrent branch integration
Qodana uses a baseline file to differentiate between legacy technical debt and new regressions. When utilizing Qodana Cloud for centralized reporting, the qodana.xml file serves as the source of truth for existing issues to prevent CI failures on established code. In a development workflow where multiple feature branches are developed concurrently, each bran