Menu

I Packed the Same Commit Twice, 200 Bytes Didn't Match
πŸ“°

I Packed the Same Commit Twice, 200 Bytes Didn't Match

DEV Community: cicdΒ·Mustafa ERBAYΒ·13 days ago
#qc1zYPFg
#devtocicd#devto#dev#gzip#enter
Reading 0:00
15s threshold

There is a single line in this blog's deploy workflow that every publication

passes through:

tar -czf - dist-deploy scripts/notify-subscribers.mjs package.json \ package-lock.json deploy/backup.sh | "$GATE" deploy

Enter fullscreen mode

Exit fullscreen mode

The build finishes, the output flows into a pipe, it is unpacked on the server

and swapped in atomically. One line above it sits this: git rev-parse HEAD >

dist-deploy/client/_v . So I can ask the server "which commit are you running"

and get the right answer back.

Two days ago I wrote about

1,190 of my cover images being impossible to reproduce :

there the problem was generation itself β€” two machines, two font engines, a

different PNG from the same input. This article is the next stop on that road.

Generation aside, is the step that packages the output deterministic? The

_v file tells me the commit but says nothing about the bytes .…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.