> The build.id property is an identifier that is unique within
> the scope of each module. It is intended to be an identifier
> useful for labeling your builds.
The problem: the version being built should be the same as
the version being labeled. Only the Draco.NET service knows
which version that is.
Conclusion: ideally, Draco.NET would label the version being
built.
To build, the following steps would be performed:
1) Label a version that needs building.
2) Request the version using the label in 1)
3) Build that version.
This has the added benefit of allowing rebuilds of older
versions at a later time.
Implementation detail: I am using SourceSafe, however this
could be applied to CVS as well.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=646474
Some helpful comments from Bernard:
From the documentation:
> The build.id property is an identifier that is unique within
> the scope of each module. It is intended to be an identifier
> useful for labeling your builds.
The problem: the version being built should be the same as
the version being labeled. Only the Draco.NET service knows
which version that is.
Conclusion: ideally, Draco.NET would label the version being
built.
To build, the following steps would be performed:
1) Label a version that needs building.
2) Request the version using the label in 1)
3) Build that version.
This has the added benefit of allowing rebuilds of older
versions at a later time.
Implementation detail: I am using SourceSafe, however this
could be applied to CVS as well.
Logged In: YES
user_id=25244
Changed summary since a tag/label needs to be set for the
version that is being built, not for the version at the time
the build is done.