the teamLastModified Ant task
Hi,
i am a bit confused by the teamLastModified Ant task.
the documentation states "The output files should be attached to the build as a log or download, so that you can maintain consistent timestamps between different streams of development."
So this would mean that the output of the task should the time stamp of the last scm change that occurred anywhere within a the structure of a given folder (down to the last file of the last sub-folder)
but when i run it i only get the time stamp of the last change to the folder itself (i.e. the last addition/removal of an artifact directly under the folder)
Is this what it is supposed to to do?
if so, what would be a use case for this task?
also the task only allows me to point to the root of my sandbox, and therefore only scans the root folders of the loaded components
rgds,
d.
i am a bit confused by the teamLastModified Ant task.
the documentation states "The output files should be attached to the build as a log or download, so that you can maintain consistent timestamps between different streams of development."
So this would mean that the output of the task should the time stamp of the last scm change that occurred anywhere within a the structure of a given folder (down to the last file of the last sub-folder)
but when i run it i only get the time stamp of the last change to the folder itself (i.e. the last addition/removal of an artifact directly under the folder)
Is this what it is supposed to to do?
if so, what would be a use case for this task?
also the task only allows me to point to the root of my sandbox, and therefore only scans the root folders of the loaded components
rgds,
d.
4 answers
david.brpr wrote:
Join the club. The teamLastModified Ant task is somewhat confusing. To
some extent it was put together in a hurry so that the builds of RTC
itself could have correct version qualifiers for the plugins. It was
never fully polished, so it still has some rough edges.
Close. Actually it is the creation time of the oldest baseline visible
in the workspace that was created after the last SCM change anywhere
within the given folder. So if your workspace doesn't have regularly
created baselines, teamLastModified won't do you much good.
(I have no idea if this is actually the cause of your problem. But it
is one possible thing to check.)
Yes, that is an unfortunate limitation.
i am a bit confused by the teamLastModified Ant task.
Join the club. The teamLastModified Ant task is somewhat confusing. To
some extent it was put together in a hurry so that the builds of RTC
itself could have correct version qualifiers for the plugins. It was
never fully polished, so it still has some rough edges.
So this would mean that the output of the task should the time stamp
of the last scm change that occurred anywhere within a the structure
of a given folder (down to the last file of the last sub-folder)
Close. Actually it is the creation time of the oldest baseline visible
in the workspace that was created after the last SCM change anywhere
within the given folder. So if your workspace doesn't have regularly
created baselines, teamLastModified won't do you much good.
(I have no idea if this is actually the cause of your problem. But it
is one possible thing to check.)
also the task only allows me to point to the root of my sandbox, and
therefore only scans the root folders of the loaded components
Yes, that is an unfortunate limitation.
Hi David,
If the teamLastModified Ant task isn't working the way you expect, or require for your use case, please file a work item against RTC/Build, and let us know what you need.
Regards,
Nick Edgar
RTC Build component lead
If the teamLastModified Ant task isn't working the way you expect, or require for your use case, please file a work item against RTC/Build, and let us know what you need.
Regards,
Nick Edgar
RTC Build component lead
David(s), I've filed: 94853: Allow parent directory to be specified in teamLastModified task. Please feel free to elaborate on it as needed, or file extra work items.