Home Search Pricing Get inErrata About

Sign in Sign up

Graph/workflow-artifact-path-drift

AntiPattern

Workflow Artifact Path Drift

workflow-artifact-path-drift

CI/CD workflows fail to locate or correctly propagate generated build artifacts because path and file-location assumptions drift across steps (e.g., missing .yml workflow loading, devcontainer output paths, custom artifact-server-path), breaking downstream job behavior.

Node Details

Public graph metadata

Updated6/24/2026

Connections

30 linked nodes

MATCHESSolution

Avoid barrel file approaches because they can increase circular dependency issues

MATCHESSolution

Use peaceiris/actions-gh-pages@v3 in the Deploy step and pass github_token with the correct publish_dir

MATCHESSolution

Configure AWS Amplify to use the correct monorepo root/workspace (e.g., appRoot/workspaces/dashboard) and ensure install/build runs from that workspace so .next and the required server files are produced and packaged correctly.

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

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

I would skip the GitHub Actions artifact steps entirely — After you do “previous steps” in your first job. Outcome: commit/push changes to a separate branch or to the same Git branch.

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

Remove or adjust line 76 so the deployment points to the expected file location

MATCHESSolution

I've been working on exactly this problem and built BuildBeacon - a privacy-first CI/CD monitoring platform — supports GitHub Actions workflows. Outcome: no API access to your code or sensitive data.

MATCHESSolution

Is it possible to use `gh workflows run "workflow-name" --ref "pr-branch-name"` to trigger a CI that is not yet in the default branch? — `gh workflows run "workflow-name" --ref "pr-branch-name"`. Tension: today I can only trigger workflows that are already in the default branch. Outcome: I had the same problem using curl.

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 suggest to evaluate using a cloud storage tool — If you need to store those logs for audit or other scenarios (a longer retention time). Tension: the artifacts and log files generated by workflows are retained for 90 days before they are automatically deleted. Outcome: store them outside GitHub.

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

Store the dist folder — In GitHub Actions. Tension: to share data between jobs within a workflow. Outcome: Get the dist folder.

MATCHESSolution

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

MATCHESSolution

Dedupe the shared step into ONE function both paths call — when aligning two code paths for output parity. Tension: Copies drift, and the drift is invisible until something compares the outputs. Outcome: both paths call, so outputs match by construction.

MATCHESSolution

Build the target path using Path APIs from a fixed base directory (e.g., parentPath.resolve(...)), then verify that the resolved file remains within the intended parent directory before opening the stream. Use try-with-resources for InputStream/OutputStream to manage closing safely.

MATCHESSolution

Identify the exact transitive dependency introducing each vulnerable artifact (e.g., inspect the Maven dependency tree), upgrade or exclude/override those specific transitive versions, and re-run the scan. Use tools like Vulert playground (or similar dependency vulnerability checkers) to confirm which dependencies in the POM cause the findings and what they pull in.

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

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 Artifact Path Drift - inErrata Knowledge Graph | Inerrata