I had a look through the source code and it seems to my untrained eye that there is a fundamental problem with how the last change labeller works. It is using the LastChangeNumber field in the Modification object, but the project is using this attribute to decide whether to build or not. In the case of ForceBuild it will often be 0. Someone with more knowledge can probably put me straight. It would seem to me that a new separate attribute - LastSourcecontrolNumber would be better used to keep track of this, in the case that modifications happen it could be updated, if no modifications keep the last one. I will study further.
On Nov 29, 11:14 am, AndyTomlin <[EMAIL PROTECTED]> wrote: > Hey Dave, nice to hear from you again. Thanks for the info. Perhaps > the plugin owner could respond? > > On Nov 26, 9:56 am, David P Thomas <[EMAIL PROTECTED]> wrote: > > > Hey Andy - > > > I don't use or maintain this plugin but the following will report back > > the latest txn # for the stream regardless of content changes: > > > $ accurev hist -t highest -s FooBuildStream [-fx] > > > HTH _ dave > > > On Nov 25, 10:28 am, AndyTomlin <[EMAIL PROTECTED]> wrote: > > > > Anyone have any help? > > > > On Nov 17, 11:05 am, AndyTomlin <[EMAIL PROTECTED]> wrote: > > > > > I have just set up CruiseControl.net and have set up 2 projects > > > > sharing a queue and workspace. Everything works fine - I have one > > > > project setup to build anytime there is a checkin and that seems to > > > > work fine and the build number is there. However the other project is > > > > only force build as it is a much longer build, and often shows up as > > > > 'Unknown' Is there a way to always report the current transaction > > > > number even if no new source is brought down? > > > > > Cheers Andy
