>
> Yes, but only if you are doing a checkout/get by tag/label. :)
>
> In the case of a change to a version release tag/label, and the associated
> get on that label, can dramatically change the source used for the build.
> But I assume that right now draco doesn't support builds based on
> label/t
ch 06, 2003 8:49 AM
Subject: RE: [Draconet-users] Builds launched without changes to codebase...
> I would have thought that since tagging/labeling does not modify source
> files, no build is required. A tag/label is simply associating a name
with
> a specific version. It has no chance of
?
-MG
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Bernard
> Vander Beken
> Sent: 06 March 2003 16:26
> To: [EMAIL PROTECTED]
> Subject: RE: [Draconet-users] Builds launched without changes to
> codebase...
>
>
> Well,
: [Draconet-users] Builds launched without changes to
codebase...
> I think that it would be good to have a label for a good build,
> is there a way
> to make Draco ignore labels when detecting changes?
Yes, VssLogParser can be modified to ignore labels. Actually.. I
thought
that Bernard ha
version 1.4.1069.1872, I know it's not the latest...
-Original Message-
From: Mark Griffiths [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 06, 2003 10:13 AM
To: [EMAIL PROTECTED]
Subject: RE: [Draconet-users] Builds launched without changes to
codebase...
> I think that it
> I think that it would be good to have a label for a good build,
> is there a way
> to make Draco ignore labels when detecting changes?
Yes, VssLogParser can be modified to ignore labels. Actually.. I thought
that Bernard had already done this. What is the version stamp on the
draco.exe you are
Draco ignore labels when detecting changes?
Thanks,
Aaron
-Original Message-
From: Mark Griffiths [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 06, 2003 9:09 AM
To: [EMAIL PROTECTED]
Subject: RE: [Draconet-users] Builds launched without changes to
codebase...
BTW. The command line
BTW. The command line arguments passed to SS.EXE should be visible in
draco.log.
-MG
---
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
for complex code. Debugging C/C++ programs can leave you feeling lost and
d
Hi Aaron
Would you be able to see the command line arguments that are passed to
SS.EXE when fetching project history. You could then run this command
manually and let us know what the output is. From this we should be able to
determine why Draco thinks that a change has occurred.
-MG
> -Or
