On 12/12/2019 14:50, Thanh Ha wrote:
> On Thu, 12 Dec 2019 at 03:56, Robert Varga <nite@...
> <mailto:nite@...>> wrote:
>
>     Hello,
>
>     is there a simple way to know what is the content of a built image?
>
>     I mean
>     https://jenkins.opendaylight.org/releng/view/builder/job/builder-packer-merge-centos-7-builder/78/
>     does tell me there is a new image, but there is nothing in the logs
>     which would tell me what the actual content is.
>
>     That really makes it a matter of guessing as to what the delta between
>     "ZZCI - CentOS 7 - builder - x86_64 - 20190924-232354.3819" (currently
>     in use) and "ZZCI - CentOS 7 - builder - x86_64 - 20191201-060129.829"
>     (produced by the build above) really is.
>
>
> Hi Robert,

Hey Thanh,

> Not a super convenient way but you can use the packages_end.diff:
>
> https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/builder-packer-merge-centos-7-builder/78/packages_end.txt.gz

Yeah, that's what I assumed would be the answer, but these files are
produced for every build:
https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/yangtools-maven-verify-master-mvn35-openjdk11/616/packages_end.txt.gz

> This tells you which packages were installed into the image in that
> particular build. The hard part is tracking down the logs for the

hence correction: this tells me what packages were installed into the
image that ran the the job.

What I am after is something different: the packer job created a new
image for potential use in jobs (turtles all the way down) -- and I want
to know the contents of that new image.

One way would be to try sandbox with that image (and look at
packages_end of that job), except it seems I am too lame to be able to
get that running.