Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

This stops passing "now" as the SOURCE_DATE_EPOCH to apko. #112

Merged
merged 1 commit into from
May 23, 2023

Conversation

mattmoor
Copy link
Contributor

We have made changes to apko to compute the "build date epoch" based on MAX(installed packages builddate), which should make the image timestamp a reflection of the last time one of the packages contributing to the image changed.

This should result in significantly less nightly churn from image rebuilds where only the timestamp changes.

@mattmoor mattmoor requested a review from kaniini May 23, 2023 17:55
We have made changes to `apko` to compute the "build date epoch" based on `MAX(installed packages builddate)`, which should make the image timestamp a reflection of the last time one of the packages contributing to the image changed.

This should result in significantly less nightly churn from image rebuilds where only the timestamp changes.

Signed-off-by: Matt Moore <[email protected]>
@mattmoor
Copy link
Contributor Author

Needs: wolfi-dev/os#2264 to land first, lest we revert to the unix epoch for some images.

@mattmoor
Copy link
Contributor Author

I confirmed that an apko build pulls in the Wolfi baselayout's timestamp when this is unset, so I think this is good to go 🤞

@kaniini kaniini merged commit 0f3a6c0 into chainguard-images:main May 23, 2023
@mattmoor mattmoor deleted the use-build-date-epoch branch May 23, 2023 22:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants