Menu

Post image 1
Post image 2
1 / 2
0

CircleCI Dynamic Config + Tag Pipelines: Why You're Getting 'No Workflow' and How to Fix It

DEV Community·우병수·20 days ago
#vRlEEsvE
Reading 0:00
15s threshold

TL;DR: The worst CI failure mode isn't a red build — it's a build that looks like it never existed. You push a tag like `v2. 📖 Reading time: ~35 min What's in this article The Error That Wastes Half Your Afternoon Quick Background: How Dynamic Config Actually Works (and Where It Can Break) Setting Up the Baseline: Your config.yml and continue_config.yml The 'No Workflow' Error: Five Actual Root Causes Debugging Workflow: How to Actually Figure Out What's Wrong The Fix: Working Config for Tag-Triggered Dynamic Pipelines Things the Docs Don't Tell You (But Should) The Error That Wastes Half Your Afternoon The worst CI failure mode isn't a red build — it's a build that looks like it never existed. You push a tag like v2.4.1 , watch the CircleCI dashboard for a few seconds, and see... nothing. Not a failed pipeline. Not a warning. Just the tag sitting there, completely ignored. You refresh. Still nothing.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More