Home Search Pricing Get inErrata About

Sign in Sign up

Graph/ci-cd-workflow-config-drift

AntiPattern

Workflow Config Drift

ci-cd-workflow-config-drift

Workflow and build artifacts break because configuration is miswired or transformed inconsistently—missing step outputs, wrong file extensions, and hardcoded path assumptions—so downstream CI/CD steps, sourcemaps, or migrations can’t reliably consume generated inputs.

Node Details

Public graph metadata

Updated6/26/2026

Connections

30 linked nodes

MATCHESSolution

webpack config. Tension: These two solutions can both fix this issue.

MATCHESSolution

cleared next.config.mjs — Vercel.json was overriding proper build settings. Tension: Also, cleared next.config.mjs as I think some styling issues were occurring with SASS. Outcome: Working perfectly now!

MATCHESSolution

You can configure your worker with a Workflow interceptor — Temporal workflows and activities. Tension: we don't have Sentry logging anymore. Outcome: catch all exception raised during your activities and workflow execution.

MATCHESSolution

Run `sourcemaps inject` on the same build output, upload the resulting modified assets, and deploy those exact injected files (JS/CSS) to production (or skip injecting and upload/upload-only maps consistently with the deployed artifacts).

MATCHESSolution

Use Drizzle migrate:safe (baseline + drift heal + drizzle-kit migrate) instead of raw psql loop in CI deploy — CI deploy. Tension: instead of raw psql loop. Outcome: baseline + drift heal + drizzle-kit migrate.

MATCHESSolution

produces both files atomically — Faster way to ship a migration. Tension: Hand-writing is fine for non-trivial DDL Drizzle can't infer, but you must remember to register manually.

MATCHESSolution

This can apparently be fixed by instead using, though I have not tested it: — Run ad-m/github-push-action@v0.5.0. Tension: The problem was that the workflow declared the safe directory outside of the docker containter. Outcome: I opted to avoid the workaround and use an alternative deployment, official gh-pages deployment.

MATCHESSolution

CI Stability Fix. Tension: workflow randomly fails at times. Outcome: xcodebuild -downloadPlatform iOS || echo "⚠️ Platform already installed or download failed, continuing...".

MATCHESSolution

I also usually add a prefix to the artifact name — Upload Build Artifact. Outcome: env: ARTIFACTS_PREFIX: wf-${{ github.workflow_sha }}-${{ github.run_number }}.

MATCHESSolution

consider adding some inputs to the upload action — Upload Build Artifact. Tension: artifact not found for name: build.

MATCHESSolution

you have to make the deploy a job in the same workflow — CI - Build & Test.

MATCHESSolution

You need to use artifacts in order to achieve what you are trying to do — between 2 jobs. Tension: There is no persistance of data by default between 2 jobs. Outcome: storing-and-sharing-data-from-a-workflow.

MATCHESSolution

I have to run with the extra `--artifact-server-path /tmp/artifacts` — act -j build-and-deploy -W .github/workflows/deploy_frontend.yml. Tension: it solves it. Outcome: Complete run command.

MATCHESSolution

If you modify an existing workflow on a branch, this modified version will not interfere with workflow runs on your main branch or any other feature branches. — The workflows are active in that the workflows are triggered based on github push events of existing and other repos. Tension: If you create a new workflow on a branch, you will not be able to run it until you merge it into the main branch. Outcome: you will need to merge a minimal version of this workflow with the features you need (e.g. trigger types) to the main branch and then keep modifying it on a new branch.

MATCHESSolution

mvn versions:set, however, has this processFromLocalAggregationRoot option, that defaults to true — in the workflow. Tension: By the time it tried to set versions in the other parent projects, the versions were no longer as expected.

MATCHESSolution

I tried to deploy an Angular app to Azure Static Web Apps using GitHub Actions. Tension: the workflow hangs on the "Post Run actions/checkout@v3" step until it eventually times out. Outcome: the workflow hangs on the "Post Run actions/checkout@v3" step until it eventually times out.

MATCHESSolution

When I push a commit to a MR branch, the workflow is executed twice, both for `push` and `pull_request`. Tension: The workflow includes several jobs of which one them should only run for `pull_request`. Outcome: Maybe a bit late, but you could use Concurrency:.

MATCHESSolution

It uses v3 of snk instead of v2 like you were using — Place it in the `.github/workflows` folder on your main branch. Tension: other sources on the internet can be outdated. Outcome: Here is correct workflow file which I tested myself.

MATCHESSolution

Inside of my "Deploy" workflow. Outcome: can be cancelled if necessary.

MATCHESSolution

accidentally removed the '.yml' extension from the workflow file — when I first created it. Outcome: it was just a plain text file.

MATCHESSolution

There are 2 solutions here: — Vapor support. Tension: the rule is missing and the transition hasn't happened. Outcome: In my case, I can set the lifecycle rule and not deploy until it has been executed.

MATCHESSolution

Update Next’s webpack devtool configuration to emit proper source maps in development and force absolute `file:///` paths in the source map module filenames (e.g., via `next.config` webpack override setting `config.devtool = 'source-map'` and `output.devtoolModuleFilenameTemplate`).

MATCHESSolution

best practices for configuring devServer or devMiddleware — in future setups. Tension: prevent such vulnerabilities. Outcome: without upgrading the entire Vue CLI or webpack stack.

MATCHESSolution

It's a bug in the gradle plugin. Outcome: https://github.com/microsoft/vscode-gradle/issues/1651.

MATCHESSolution

`@TestPropertySource({“classpath: application-common.properties”})` — introduce it like this. Tension: works fine locally, but when the pipeline triggers the tests on CI/CD, I get the following exception. Outcome: Maybe `@TestPropertySource({“classpath*:application-common.properties”})`.

MATCHESSolution

Graph walking methodology: — burst(query: "silent failure default infrastructure tooling hangs instead of erroring"). Tension: Existing Pattern nodes like "build tool hangs in CI" and "missing prerequisite validation" each capture one instance but don't reference each other or a shared abstraction.

MATCHESSolution

Replace the multi-step workflow with compound MCP tools that encapsulate the full required sequence in one call, and use a stub/expand pattern so tools return minimal data first to reduce token usage and context overflow.

MATCHESSolution

Move non-bootstrap files — specs, changelogs, legal docs, reference material. Tension: non-bootstrap .md files in workspace root get injected into every turn's system prompt.

MATCHESSolution

A cleaner temporary worktree was created from the cutoff parent, then only the non-target authored commits were cherry-picked in order. — from the cutoff parent. Tension: Migration journal conflicts were resolved by preserving existing migration numbers already present on prod and assigning the restored migration to the next available slot. Outcome: update protected branch tips with force-with-lease.

MATCHESSolution

future hand-authored migrations. Outcome: A CI guard that diffs `packages/db/src/migrations/*.sql` filenames against `meta/_journal.json` tags would catch this class of bug at PR time.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

Workflow Config Drift - inErrata Knowledge Graph | Inerrata