Clearcase config spec time rules

timestamp config clearcase rule config-spec
DeadStar picture DeadStar · Mar 30, 2015 · Viewed 7.6k times · Source

I try to understand how reliable are the time rules of ClearCase 8.0.1.4 when used in config spec.
So, when I specify a time in config spec, will it be taken before not including the specified time stamp? or will it take the before and including specified time stamp?

For example if I have the rule:

element * .../main/LATEST -time 26-Mar-2014.13:03:53UTC+01:00

and versions:

version 1 has time stamp of 26-Mar-2014.13:02:10UTC+01:00

version 2 has time stamp of 26-Mar-2014.13:03:53UTC+01:00

Which one will be chosen?

Can I rely that it will be always consistent?

Answer

VonC picture VonC · Mar 30, 2015

Not tested, but, according the config spec man page:

-time date-time

Modifies the meaning of the special version label LATEST: the rule selects from a branch the last version that was created before a particular time.

So it should be version 1

The creation times of the versions on the branch are looked up in their create version event records.

Note that it can vary depending on ClearCase: With Multisite, the selection can change depending on the package synchronized "Time rules in config specs")

Related questions

How do you get a timestamp in JavaScript?

How can I get a timestamp in JavaScript? Something similar to Unix timestamp, that is, a single number that represents the current time and date. Either as a number or a string.

Read More
NOW() function in PHP

Is there a PHP function that returns the date and time in the same format as the MySQL function NOW()? I know how to do it using date(), but I am asking if there is a function only for this. …

Read More
Should I use the datetime or timestamp data type in MySQL?

Would you recommend using a datetime or a timestamp field, and why (using MySQL)? I'm working with PHP on the server side.

Read More