ArchitectureDeploy pipeline
A deploy log
The deploy log shows each step of the pipeline, with the output of the build and of the containers.
Deploy log
$ ferry logs --deploy dep-3271cdfd1415400d9a5e09:38:58 ==> Starting deploy dep-3271cdfd1415400d9a5e (trigger: blueprint)09:38:58 ==> Using image nginx:alpine (already present)09:38:58 ==> Pinned nginx:alpine as docsc3/hello:dep-3271cdfd1415400d9a5e09:38:58 ==> Using port 80 (service setting)09:38:58 ==> Limits: 512 MiB memory, 1 CPU per instance09:38:58 ==> Starting 2 instance(s)09:38:58 ==> Started instance 9c5087 (port 80, published on 127.0.0.1:63120)09:38:58 ==> Started instance 77122e (port 80, published on 127.0.0.1:63121)09:38:58 ==> Waiting for 2 instance(s) to become healthy: GET / must answer with a status below 400 (timeout 120s)09:38:59 ==> Health check passed09:38:59 ==> Routing traffic to the new instance(s)09:38:59 ==> Your service is live 🎉09:38:59 ==> Available at http://hello.localhost:18091This deploy log is from an image deploy of a web service with two instances.
The lines that start with ==> come from Ferry. The other lines are the output of the build or of the containers.
Which step writes which line
| Lines | Step |
|---|---|
Using image, Pinned | Build |
Using port, Limits | Snapshot |
Starting, Started instance | Start |
Waiting for, Health check passed | Health check |
Routing traffic, Your service is live | Switch |
For the commands that read a log, see History and logs.