WED
WED Pipeline
World Economic Database · cloud build
weekly · Wed 02:00
Representative run. No live GitHub Actions run has reported yet, so the hero, flow, timeline and run details below show the shape of a completed weekly build (anchored to the current release). They bind to real per-job status & timings the moment a run fires — the webhook + heartbeat endpoints are ready. The release data & change tracking further down is live.
Latest build succeeded
Version — published to wed-output-ap1 · ran 2h 31m
Succeeded
weekly · Wed 02:00
Version
—
S3 output prefix
Duration
2h 31m
across 16 steps
Trigger
Scheduled
weekly cadence
Cadence
Weekly
Wed 02:00 · self-hosted/wed
Pipeline flow
8 phases · click a phase to jump to its steps
Setup
16s
Configure
5s
Acquire data
6m 12s
Build
2h 14m
Validate
18s
Publish
5m 30s
Ingest
5m 0s
Cleanup
23s
Where the time goes
the Stata build dominates total runtime
Setup
16s
Configure
5s
Acquire data
6m 12s
Build
2h 14m
Validate
18s
Publish
5m 30s
Ingest
5m 0s
Cleanup
23s
00:00start → finish · total 2h 31m2h 31m
Steps & logs
grouped by phase · expand for detail
Run details
representative
Execution
Trigger
Scheduled (weekly)
Actor
github-actions[bot]
Started
—
Finished
running…
Runner
self-hosted · linux · wed · ap-southeast-1
Run options
run_mitchell: falseskip_pull: false
Outputs & artifacts
s3://wed-output-ap1/—/final
1.4 GiB · final WED release
s3://wed-archive-ap1/—
clean_data_wide.dta + run_report.json · vintage backup
wed_staging · —
release sealed · change events emitted
Data flow
gmd-wed-data-ap1buildwed-output-ap1ingestwed_staging
Source health
per-source execution · finer than GH jobs & steps
Loading source health…
Release data & change tracking · live
Loading release ledger…
WED Pipeline · internal dashboardrelease —source —