FIX - removed timestamp from the tag of docker images built #3784
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Coduz
approved these changes
May 30, 2023
Codecov Report
@@ Coverage Diff @@
## develop #3784 +/- ##
=============================================
+ Coverage 49.19% 51.45% +2.26%
Complexity 26 26
=============================================
Files 1865 1866 +1
Lines 35275 35284 +9
Branches 2786 2782 -4
=============================================
+ Hits 17352 18155 +803
+ Misses 17003 16176 -827
- Partials 920 953 +33
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On Kapua, other than images tagged as the latest and with the version number, a set of images tagged with the current timestamp is created during the build. If this feature could be useful in some contexts, where for example daily builds are performed and you need to save a temporal snapshot of images, this is needless in our context and, mainly, creates overhead because for each different timestamp (currently it has a granularity of 1 day) a new image is created which occupies memory on disk, resulting in a prune of images after some time to save disk space if the building is repeated over time.
This PR removes the timestamped tagged images being built.