Truncated build log question.

[Ross Lazarus]

Is it just me, or is useful/important summary output from a Dockerfile build now not appearing in the build logs or on the build progress page?

The logs I see this morning are being truncated in the interface to the extent that the second RUN... part is not even listed in the build here: https://quay.io/repository/fubar2/galaxy_toolfactory/build/93128201-2956-4330-a934-2d0acedf165c

Previously, the build page showed the separate second "RUN" section that is in the Dockerfile. Today that seems to have been truncated and the single RUN section showing in this image expands only about 2/3 of the way through what a local build will show.

This is not a big deal for me as the image is correct but it is not ideal to have the log truncated without any obvious signs that this has happened - is this expected behaviour or a bug?

[Daniel Messer]

Hi Ross,

this is definitely not expected. A couple of things: 

• is this a reproducible issue? If so, can you share the latest build job id? (the uuid in the URL)
• is the Dockerfile the build job uses definitely the same that you use locally? 
• can you paste the full screenshot to show the truncation? It looks like your screenshot is cropped
• does this also happen when you create the same build trigger config in another repository inside your org?

Best,

Daniel

--
You received this message because you are subscribed to the Google Groups "quay-sig" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quay-sig+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/quay-sig/57d150d2-6b4c-47f8-bfcf-f0d750ee571en%40googlegroups.com.

--

Daniel Messer

Product Management

Red Hat OpenShift