-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Enable lazy evaluation of jib.container.creationTime and jib.container.filesModificationTime #3708
Comments
…ib.container.filesModificationTime (GoogleContainerTools#3708)
Thank you for creating this issue and opening the PR @creckord! As mentioned in the PR, we will wait for the CLA to signed to review your contribution. |
Just a quick life sign - it took a bit for the CLA to pass our legal, but I have that now, right in time for my 3-week vacation in offline land. I'll fix the open issues in the PR when I'm back. |
Thank you! |
…ers with Property (GoogleContainerTools#3708) * Removes String getters/setters * Adds getter for Property instead
…ib.container.filesModificationTime (GoogleContainerTools#3708)
…ers with Property (GoogleContainerTools#3708) * Removes String getters/setters * Adds getter for Property instead
…ers with Property (GoogleContainerTools#3708) * Removes String getters/setters * Adds getter for Property instead
…ers with Property (GoogleContainerTools#3708) * Removes String getters/setters * Adds getter for Property instead
|
Similar to what #2727 did for image name and tags, it would be great to be able to have lazy evaluation for
creationTime
andfilesModificationTime
, e.g. to set times to the latest commit time provided bygradle-git-properties
(see also #2317).Currently, this is not easily possible, since the value in the plugin config is eagerly bound before the git properties are set. I.e. this does not work:
The text was updated successfully, but these errors were encountered: