-
Notifications
You must be signed in to change notification settings - Fork 293
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
Set SOURCE_DATE_EPOCH #1418
Set SOURCE_DATE_EPOCH #1418
Conversation
…ag is provided Signed-off-by: Natalie Arellano <narellano@vmware.com>
Codecov Report
@@ Coverage Diff @@
## main #1418 +/- ##
==========================================
- Coverage 81.27% 81.27% -0.00%
==========================================
Files 151 151
Lines 9715 9745 +30
==========================================
+ Hits 7895 7919 +24
- Misses 1346 1350 +4
- Partials 474 476 +2
Flags with carried forward coverage won't be shown. Click here to find out more. |
Should the flag instead be |
Signed-off-by: Natalie Arellano <narellano@vmware.com>
Signed-off-by: Natalie Arellano <narellano@vmware.com>
9e16eaa
to
5b29c8b
Compare
Phew! Finally green... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two minor points:
- We should probably cary the term
CreationTime
across the entire code base instead of having an ambiguousDateTime
- Isn't this variable only respected on newer Platform API versions? If so, it seems like we should only be passing it to the container in those cases and warning the user if it's not applicable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall, as always, beautiful! just a few tweaks would be awesome
Signed-off-by: Natalie Arellano <narellano@vmware.com>
…en platform api is 0.9 Signed-off-by: Natalie Arellano <narellano@vmware.com>
The tests are green but I don't understand why - https://github.com/buildpacks/pack/runs/6009113466?check_suite_focus=true uses a lifecycle that doesn't support this feature. Investigating. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fantastic!
}) | ||
|
||
when("not provided", func() { | ||
it("image has create time of Jan 1, 1980", func() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This test could actually run in all compatibility cases, but I'm not sure whether it's worth the time cost of having the tests do that.
…n time Signed-off-by: Natalie Arellano <narellano@vmware.com>
Jan 1, 1980 is always going to be less than a time of about now Signed-off-by: Natalie Arellano <narellano@vmware.com>
I found the issue - fixed in c23e970 (it was a bad assertion). |
Thank you so much! This is a long-awaited feature and I am so grateful it landed! |
pack should set SOURCE_DATE_EPOCH in exporter's env if --creation-time flag is provided
Also bumps default lifecycle version
Before
Image create time is always Jan 1, 1980
After
Image create time is configurable
Documentation
Related
Resolves #1281