webapp-build command should output something about the container built #644

New Issue

dboreham · 2023-11-14T14:35:43Z

dboreham commented

2023-11-14 14:35:43 +00:00

When I build a container, the tail of output looks like this:

+ First Load JS shared by all              226 kB
  ├ chunks/framework-dd27ef4d8b61fe81.js   45.3 kB
  ├ chunks/main-2e078cccf6df721e.js        28.7 kB
  ├ chunks/pages/_app-98fe2c3c1a407c32.js  146 kB
  ├ chunks/webpack-89497964fdeb6be8.js     1.99 kB
  └ css/6f911b5efacf142b.css               3.88 kB

λ  (Server)  server-side renders at runtime (uses getInitialProps or getServerSideProps)

Removing intermediate container fe7a398251ae
 ---> 4f096a4a1408
Successfully built 4f096a4a1408
Successfully tagged cerc/iglootools-home:local

What's Next?
  View a summary of image vulnerabilities and recommendations → docker scout quickview
$

While the container tag is visible in this output, I don't think it's sufficiently obvious for the casual user. Also the docker build command could change its output in the future. Therefore our code should clearly output the result of the build. Something like:

Build host container for <source repo> with tag: <image-tag>
To test locally run: <docker run command to run this container image>
$

When I build a container, the tail of output looks like this: ``` + First Load JS shared by all 226 kB ├ chunks/framework-dd27ef4d8b61fe81.js 45.3 kB ├ chunks/main-2e078cccf6df721e.js 28.7 kB ├ chunks/pages/_app-98fe2c3c1a407c32.js 146 kB ├ chunks/webpack-89497964fdeb6be8.js 1.99 kB └ css/6f911b5efacf142b.css 3.88 kB λ (Server) server-side renders at runtime (uses getInitialProps or getServerSideProps) Removing intermediate container fe7a398251ae ---> 4f096a4a1408 Successfully built 4f096a4a1408 Successfully tagged cerc/iglootools-home:local What's Next? View a summary of image vulnerabilities and recommendations → docker scout quickview $ ``` While the container tag is visible in this output, I don't think it's sufficiently obvious for the casual user. Also the docker build command could change its output in the future. Therefore our code should clearly output the result of the build. Something like: ``` Build host container for <source repo> with tag: <image-tag> To test locally run: <docker run command to run this container image> $ ```

Sign in to join this conversation.

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/stack-orchestrator#644