Hosting Operations
List Newest Build Artifacts
A deployment references an artifact, but you are not sure which files were built most recently.
Command
find artifacts/ -type f -printf '%TY-%Tm-%Td %TH:%TM %10s %p\n' | sort | tail -20
What changed
Nothing changes. The command prints artifact timestamps, sizes, and paths.
Danger
safe
When to use it
Use before deploys, rollbacks, or artifact handoffs.
When not to use it
Do not use it for remote artifact stores unless they are mounted locally.
Undo or recovery
No undo needed because this command is read-only.
Expected output
The newest artifact files sorted by timestamp.
demo script
Disposable terminal steps
find artifacts/ -type f -maxdepth 1 -printfind artifacts/ -type f -printf '%TY-%Tm-%Td %TH:%TM %10s %p\n' | sort | tail -20
simulated output
What it looks like
::fixture-ready::
$ find artifacts/ -type f -maxdepth 1 -print
artifacts/checksums.txt
artifacts/app.tar.gz
::exit-code::0
$ find artifacts/ -type f -printf '%TY-%Tm-%Td %TH:%TM %10s %p\n' | sort | tail -20
2026-06-25 13:19 13 artifacts/app.tar.gz
2026-06-25 13:19 18 artifacts/checksums.txt
::exit-code::0
YouTube Short
What did CI build?
Before deploying, list the newest artifact files with timestamps and sizes. It is a fast sanity check.
LinkedIn hook
Confirm what your pipeline actually produced before you deploy it.
Question: Do you verify artifacts before deploy, or trust the pipeline name?
experiments
A/B tests to run
Metric: save_rate
A: What did CI build?
B: Check artifacts before deploy.