display hashes in the build list and "other builds with the same hash" #6

it would be good for every unikernel build to display "other builds that resulted in the same hash" (maybe in the top-right as a list).

in the list of unikernel builds, next to the timestamp (and build status) the hash of the unikernel binary should be displayed.

it would be good for every unikernel build to display "other builds that resulted in the same hash" (maybe in the top-right as a list). in the list of unikernel builds, next to the timestamp (and build status) the hash of the unikernel binary should be displayed.

related to this topic, there are two jobs producing the same unikernel hash:

but they have different inputs:

system-packages (the pkg package was updated)
opam switch have different hashes

It would be nice to have a condensed view of the differences (maybe initially be able -- similarly to #11 -- to view the output of diff -ru between the two build outputs)

related to this topic, there are two jobs producing the same unikernel hash: - https://builder-web.robur.coop/job/retreat/build/1b103edd-6ae4-484c-aeeb-daf60a230696/ - https://builder-web.robur.coop/job/retreat/build/e44a72f3-134c-4b0f-9b89-1b58c5c43a76/ but they have different inputs: - system-packages (the pkg package was updated) - opam switch have different hashes It would be nice to have a condensed view of the differences (maybe initially be able -- similarly to #11 -- to view the output of `diff -ru` between the two build outputs)

Coming back here, indeed there are three things I'd like to suggest:

a diff between all (opam-switch (if the content of an opam file changed, it would be nice to get a more detailed change than "builder.0.0.1~dev changed"), build-environment, system-packages)
for browsing a job, condense the list of jobs that resulted in the same hash
- build A0 hash Y0
- build A1 hash Y0
- build A2 hash Y0
- build A3 hash Y1
  should just be:
- build A0 hash Y0
- build A3 hash Y3
when browsing a specific build, have a list of "other builds with the same hash" and a "diff build" link (see above, including opam-switch, build-environment, and system-packages)

When that is done, I guess rebuilding a specific build can be smoothly integrated (database stores the full information, it's just a question of presentation).

Coming back here, indeed there are three things I'd like to suggest: - a diff between all (opam-switch (if the content of an opam file changed, it would be nice to get a more detailed change than "builder.0.0.1~dev changed"), build-environment, system-packages) - for browsing a job, condense the list of jobs that resulted in the same hash - build A0 hash Y0 - build A1 hash Y0 - build A2 hash Y0 - build A3 hash Y1 should just be: - build A0 hash Y0 - build A3 hash Y3 - when browsing a specific build, have a list of "other builds with the same hash" and a "diff build" link (see above, including opam-switch, build-environment, and system-packages) When that is done, I guess rebuilding a specific build can be smoothly integrated (database stores the full information, it's just a question of presentation).

I did some improvements to the compare view in #48.

In be26e56fd4 we now emit links to compare to other builds that resulted in the same artifact.

And 6ec40365ab provides an input_id (in the build table) to slim these lists further.

In be26e56fd4fb82b9dfb769a15d3fecf75b0af33b we now emit links to compare to other builds that resulted in the same artifact. And 6ec40365abb1c271e07e9d7a54a8ef7ca8f9145a provides an `input_id` (in the build table) to slim these lists further.

meged into the main branch

Labels Milestones

display hashes in the build list and "other builds with the same hash" #6