| RE: [cdt-dev] CDT builds now tagged |
|
No worries now J. The platform tags, but it is all based on
their magic map files and every plugin can have a different tag. I’ve
kludged ours so that everything uses the timestamp. (For the curious, the
timestamp was the time the <timestamp> ant command ran near the beginning
of the build) We may wish to follow the exact same
process as the platform team, but that would require too much of my time at the
moment to get done correctly. Maybe 4.0… Doug Schaefer, QNX Software Systems Eclipse CDT Project Lead, Tools PMC member From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Recoskie, Chris Sweet… now if
we could just get the platform to do the same :-( I don’t know what
everyone else does but we typically have to resort to fetching via the
timestamp that was in the qualifier for the I-build. Messy.
Probably not correct either as it’s never clear to me exactly when that
timestamp is applied. Is it the start of the build? The end?
Somewhere in between? ___________________________________________ Chris Recoskie Software Designer http://eclipse.org/cdt From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer Hey gang, I am now tagging all files that go into each CDT build. This
will allow us to reproduce these builds accurately if needed. The tags are
v<build number>, the build number also appears as the fourth qualifier in
the version of the plugins. This is all automagic in the build.xml file in the
cdt.releng project. And there was much rejoicing, at least from my brethren here
at QNX, but I know others have been interested in seeing this in the past as
well. Cheers, Doug Schaefer, QNX Software Systems Eclipse CDT Project Lead, Tools PMC member |