Jira (PUP-10257) Mark environments when superseded

[Justin Stoller (JIRA)]

Justin Stoller updated an issue

Puppet / PUP-10257 Mark environments when superseded Change By: Justin Stoller Summary: Write timestamp to file in environment Mark environments when beginning compilation superseded Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

[Justin Stoller (JIRA)]

Justin Stoller updated an issue

Puppet / PUP-10257 Mark environments when superseded Change By: Justin Stoller

In order to clean up old versions Note: A previous version of the code dir when using the new this ticket suggested writing timestamps to a file -sync layout, we need by Puppet's compiler (a proposed naive workaround to know whether or not those versions are still in use for compilation being able to rely on "atime" being available from the filesystem) . Since not all systems report access time for files, we need Subsequent discussion moved to record this metadata ourselves writing timestamps when an environment was superseded (ie another version of the same environment was deployed) . Puppet should write Consequently, some of the current time conversation in this ticket are no longer applicable and this ticket was moved from PUP to CODEMGMT. When deploying a file in the new lockless environment when it begins version, write a compilation for that env. The timestamp to a known file -sync client can then later reference specifying when other versions of this file to decide whether or not to purge the directory environment were superseded . Needs further specification...

Add Comment