Incident Dossier

The Artifact That Belonged To Yesterday

A CI pipeline uploads a build artifact at the end of each run. Downstream deploys then download that artifact. Today's deploy reached into the bucket and pulled an object whose name began with yesterday's runId — the same artifact that was supposed to be replaced had been quietly reused. The URL the orchestrator passed to the deploy step looked reasonable on the surface; it just happened to refer to the wrong runId.

Initial failing signaluploadArtifact('run-B') returns the URL built for 'run-A'Expected behavior: uploadArtifact('run-B',...).url matches /run-B/ · actual behavior: uploadArtifact('run-B',...).url matches /run-A/

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Run npm test.
Inspect uploadArtifact in src/artifact-uploader.js.
Notice that the function caches the first record and short-circuits before constructing a new one.
Make the function return a fresh record for every call.

Focus Mode

Start

src/artifact-uploader.js

Likely area

src/artifact-uploader.js

Challenge Coach

Hints reveal broad direction first, then narrow toward the suspect path without showing hidden tests or exact solution code.

TopicCI/CD & Pipelines

DifficultyMedium

Est. time18 min

Workspacepreparing

Explorer

Loading files

Evidence Map

Failing signal loaded from challenge API
Workspace files loaded from workspace API
Results rendered only after API run/submit

Autosaved

workspace

Outputread-onlyready$ prepare workspace

Preparing workspace