Green CI checks can mask untested release pipeline steps, developer warns

·4 views

A developer discovered that two consecutive green CI runs on a release pipeline were misleading — both passed because the tool, python-semantic-release, correctly detected no release was needed and exited early without executing the critical push step. Since the triggering commits were of types like 'docs:' and 'ci:', which do not warrant a version bump, the pipeline short-circuited before ever testing the protected-branch push or the release token. A separate bug also revealed that build artifacts were not automatically staged for commit, meaning they were silently absent from releases despite all job steps exiting with code 0. The author argues that a zero exit code only confirms a command ran without error, not that it performed the intended work. The key takeaway is that engineers should verify actual pipeline effects — such as whether a tag was created or artifacts were staged — rather than relying solely on a passing status badge.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Single Responsibility Principle: Why Each Class Should Do Only One Thing

The Single Responsibility Principle (SRP) states that a class should have only one reason to change, meaning it should handle just one distinct responsibility. Classes that bundle multiple concerns — such as validation, database access, notifications, and logging — are known as God Classes and are considered an anti-pattern in software design. A useful analogy compares a Swiss Army knife, which breaks as a whole unit when one tool fails, to a scalpel, which is purpose-built and replaced only when it specifically malfunctions. In practice, SRP underpins popular architectural patterns like MVC, Hexagonal, and Clean Architecture, where each layer owns a clearly defined role. Refactoring a bloated class into focused units — such as separate classes for validation, persistence, and email — makes codebases easier to maintain, test, and scale.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Single Responsibility Principle: Why Each Class Should Do Only One Thing

The Single Responsibility Principle (SRP) is a foundational software design concept stating that a class should have only one reason to change. Classes that handle multiple responsibilities — such as validation, database access, notifications, and logging all at once — are known as 'God Classes' and are considered an anti-pattern. A useful analogy compares a Swiss Army knife, which is versatile but fragile as a whole, to a scalpel, which is purpose-built and easier to maintain. In practice, SRP encourages splitting responsibilities into dedicated classes, such as separating UserValidator, UserRepository, EmailService, and Logger into distinct units. This principle aligns closely with layered architectures like MVC, Hexagonal, and Clean Architecture, where each layer owns a clearly defined responsibility.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Python Tool Lets Developers Validate LLM Workflow Graphs Before Runtime Errors Strike

A tutorial published on DEV Community introduces a method to validate large language model (LLM) workflow structures at load time, before any user interaction occurs. The approach models LLM workflows as directed graphs in YAML, where each step declares permitted transitions, re-entry rules, and invocation limits. Using the open-source Python package llm-workflow-router, developers can run topology checks that flag broken transitions, unreachable steps, and unresolvable loops before execution begins. The method targets structural bugs — such as a step referencing a non-existent target — that traditional runtime guardrails like retry caps or timeouts can only limit, not prevent. The tutorial argues that catching these errors at configuration load time eliminates an entire class of silent production failures that are otherwise difficult to trace.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why Industrial IoT Sensor Data Is Less Reliable Than Developers Assume

A technical guide published on DEV Community walks software developers through the full data pipeline of an industrial IoT system, from a physical sensor to a cloud application. The piece explains that temperature sensors like PT100 detectors carry inherent measurement tolerances — up to ±1.3°C — and can drift further over years of uncalibrated use. Signal conversion via 4-20mA transmitters introduces additional sources of error, including electrical noise, quantisation limits, and misconfigured scaling ranges. PLC scan cycles mean fast physical events can go undetected, and timestamps often reflect when data was polled rather than when an event actually occurred. The guide urges developers working on the software side to account for these hardware-layer uncertainties when designing alerts, thresholds, and data quality checks.

0 comments Read more at DEV Community