Re: Blame Mechanism
Emmanuel Venisse schrieb: Mac-Systems a écrit : On Continuum Website :http://maven.apache.org/continuum/continuum-features.html stands it supports Blame Mechanism. How can i benefit from it ? And how to use it! It isn't a real blame mechanism. In the build result page, you can see files modified since the latest build with the change date and the committer. Sounds a bit like what i wanted (see my notify mail question from yesterday). PS: Whats up with the Continuum Wiki ? The wiki is there: http://docs.codehaus.org/display/CONTINUUMUSER/Home Ahh. I have to sign up first :)
Re: Blame Mechanism
Mac-Systems a écrit : On Continuum Website :http://maven.apache.org/continuum/continuum-features.html stands it supports Blame Mechanism. How can i benefit from it ? And how to use it! It isn't a real blame mechanism. In the build result page, you can see files modified since the latest build with the change date and the committer. PS: Whats up with the Continuum Wiki ? The wiki is there: http://docs.codehaus.org/display/CONTINUUMUSER/Home
Re: CVS Blame mechanism in 1.0.3
The last bullet on this page: http://maven.apache.org/continuum/continuum-features.html says that Blame mechanism is available as a feature. But I do not see it. DO I need to turn it on somehow? Can somebody please help me in pointing me in the right direction? We use CVS with Ant to build. Thanks, Anoop On 9/7/06, Anoop kumar V <[EMAIL PROTECTED]> wrote: Hi, We use Continuum 1.0.3. It is a great and very focussed product - thank you, developers. We use CVS as our SCM - but when a build fails, we only see a list of changed files and no other information about those files - like who checked it in - comments etc.. I read somewhere that the blame mechanism works in 1.0.3 - Is there some special configuration I need to do - or maybe tweak my cvs.. please let me know. -- Thanks and best regards, Anoop -- Thanks and best regards, Anoop
CVS Blame mechanism in 1.0.3
Hi, We use Continuum 1.0.3. It is a great and very focussed product - thank you, developers. We use CVS as our SCM - but when a build fails, we only see a list of changed files and no other information about those files - like who checked it in - comments etc.. I read somewhere that the blame mechanism works in 1.0.3 - Is there some special configuration I need to do - or maybe tweak my cvs.. please let me know. -- Thanks and best regards, Anoop
RE: Blame mechanism with SVN
I was wrong about it being just on 1 commit. It is almost always missing although I have occasionally seen it. I created a jira: http://jira.codehaus.org/browse/CONTINUUM-827 -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Monday, August 21, 2006 5:42 AM To: continuum-users@maven.apache.org Subject: Re: Blame mechanism with SVN Normally, it must work for more than one commit (a sample with 2 commit: http://ci.codehaus.org:8001/continuum/servlet/continuum/target/ProjectBuild.vm?view=ProjectBuild&buildId=50822&id=1) If it doens't work for you with more than one commit, it's a bug. Emmanuel Binil Thomas a écrit : > Thanks for posting Brian. That is encouraging news. I would really > like to see this information in the failure emails. > > Is this a Contiuum bug or is there some involved reasoning behind > providing this info only if there a single commit? > > Thanks, > Binil > > On 8/20/06, Brian E. Fox <[EMAIL PROTECTED]> wrote: >> Paying more attention now, I noticed that is seems like continuum >> only does this if there was just 1 commit since the last build. If >> not, all you get it a list of files. >> >> -Original Message- >> From: Binil Thomas [mailto:[EMAIL PROTECTED] >> Sent: Saturday, August 19, 2006 12:46 AM >> To: continuum-users@maven.apache.org >> Subject: Re: Blame mechanism with SVN >> >> Same here; and that was what my original post was about. >> >> From previous posts here, I expected the notification email to have >> not just the list of changed files, but also the authors of those >> changes (date and commit comments, if available, would be real nice too). >> >> From the logs (which I had posted earlier), I can see that Continuum >> does issue an svn log command. Also, when I try the same command on >> the console, I do get the required data from the SVN server. >> >> Has anyone got this working on their Continuum 1.0.3 installation? >> >> Thanks, >> Binil >> >> On 8/18/06, Brian E. Fox <[EMAIL PROTECTED]> wrote: >> > That's more than I get now. I only get a list of files changed: >> > >> > >> > Changes >> > >> application\std-interview\src\main\java\com\stchome\dsms\appl\formdat >> asources\stdinterview\InterviewTravelHistoryListHelper.java >> >> > >> application\std-interview\src\main\java\com\stchome\dsms\appl\formdat >> asources\stdinterview\InterviewTravelHistoryHelper.java >> >> > >> > application\std-interview\src\main\java\com\stchome\dsms\appl\formd >> > ata sources\stdinterview\InterviewTravelAndNotesHelper.java >> > >> > I'm using 1.0.3so how do I turn on the other info? >> > >> > -Original Message- >> > From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] >> > Sent: Friday, August 18, 2006 9:19 AM >> > To: continuum-users@maven.apache.org >> > Subject: Re: Blame mechanism with SVN >> > >> > It isn't really the svn blame mechanism but only the list of >> > changes in the build result screen with (author, date, modified >> > files and commit comments) >> > >> > Emmanuel >> > >> > Brian E. Fox a écrit : >> > > Actually, I mean turn on the svn blame output in continuum. >> > > >> > > -Original Message- >> > > From: Binil Thomas [mailto:[EMAIL PROTECTED] >> > > Sent: Friday, August 18, 2006 1:57 AM >> > > To: continuum-users@maven.apache.org >> > > Subject: Re: Blame mechanism with SVN >> > > >> > > Brian, >> > > >> > > I assume that you meant the logs when you asked "How do you turn >> this on?". >> > > >> > > I do not remember doing anything special for turning on the logs. >> I think they are configured in the >> $CONTINUUM_HOME/apps/continuum/conf/application.xml file - look for >> the component 'Logger manager'. For my installation, this component >> is configured as: >> > > >> > > >> > > >> > > org.codehaus.plexus.logging.LoggerManager >> > > >> org.codehaus.plexus.logging.log4j.Log4JLoggerManager< >> /implementation> >> >> > > basic >> > > >> > > >> > > DEBUG >> > > console,rolling >
Re: Blame mechanism with SVN
Normally, it must work for more than one commit (a sample with 2 commit:
http://ci.codehaus.org:8001/continuum/servlet/continuum/target/ProjectBuild.vm?view=ProjectBuild&buildId=50822&id=1)
If it doens't work for you with more than one commit, it's a bug.
Emmanuel
Binil Thomas a écrit :
Thanks for posting Brian. That is encouraging news. I would really
like to see this information in the failure emails.
Is this a Contiuum bug or is there some involved reasoning behind
providing this info only if there a single commit?
Thanks,
Binil
On 8/20/06, Brian E. Fox <[EMAIL PROTECTED]> wrote:
Paying more attention now, I noticed that is seems like continuum only
does this if there was just 1 commit since the last build. If not, all
you get it a list of files.
-Original Message-
From: Binil Thomas [mailto:[EMAIL PROTECTED]
Sent: Saturday, August 19, 2006 12:46 AM
To: continuum-users@maven.apache.org
Subject: Re: Blame mechanism with SVN
Same here; and that was what my original post was about.
From previous posts here, I expected the notification email to have
not just the list of changed files, but also the authors of those
changes (date and commit comments, if available, would be real nice too).
From the logs (which I had posted earlier), I can see that Continuum
does issue an svn log command. Also, when I try the same command on
the console, I do get the required data from the SVN server.
Has anyone got this working on their Continuum 1.0.3 installation?
Thanks,
Binil
On 8/18/06, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> That's more than I get now. I only get a list of files changed:
>
>
> Changes
>
application\std-interview\src\main\java\com\stchome\dsms\appl\formdatasources\stdinterview\InterviewTravelHistoryListHelper.java
>
application\std-interview\src\main\java\com\stchome\dsms\appl\formdatasources\stdinterview\InterviewTravelHistoryHelper.java
>
> application\std-interview\src\main\java\com\stchome\dsms\appl\formdata
> sources\stdinterview\InterviewTravelAndNotesHelper.java
>
> I'm using 1.0.3so how do I turn on the other info?
>
> -Original Message-
> From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 18, 2006 9:19 AM
> To: continuum-users@maven.apache.org
> Subject: Re: Blame mechanism with SVN
>
> It isn't really the svn blame mechanism but only the list of changes
> in the build result screen with (author, date, modified files and
> commit comments)
>
> Emmanuel
>
> Brian E. Fox a écrit :
> > Actually, I mean turn on the svn blame output in continuum.
> >
> > -Original Message-
> > From: Binil Thomas [mailto:[EMAIL PROTECTED]
> > Sent: Friday, August 18, 2006 1:57 AM
> > To: continuum-users@maven.apache.org
> > Subject: Re: Blame mechanism with SVN
> >
> > Brian,
> >
> > I assume that you meant the logs when you asked "How do you turn
this on?".
> >
> > I do not remember doing anything special for turning on the logs.
I think they are configured in the
$CONTINUUM_HOME/apps/continuum/conf/application.xml file - look for
the component 'Logger manager'. For my installation, this component is
configured as:
> >
> >
> >
> > org.codehaus.plexus.logging.LoggerManager
> >
org.codehaus.plexus.logging.log4j.Log4JLoggerManager
> > basic
> >
> >
> > DEBUG
> > console,rolling
> >
> >
> > console
> > DEBUG
> > org.apache.log4j.ConsoleAppender
> > %d [%t] %-5p %-30c{1} -
%m%n
> >
> >
> >
> > rolling
> > DEBUG
> > org.apache.log4j.RollingFileAppender
> > %-4r [%t] %-5p %c %x -
> > %m%n
> >
> >
> >
> > file
> > ${plexus.home}/logs/continuum.log
> >
> >
> > append
> > true
> >
> >
> > maxBackupIndex
> > 10
> >
> >
> > maxFileSize
> > 10MB
> >
> >
> >
> >
> >
> >
> >
org.apache.maven.continuum.execution.maven.m2.MavenBuilderHelper
> > INFO
> >
> >
> > org.codehaus.plexus.velocity
> > WARN
> >
RE: Blame mechanism with SVN
That's more than I get now. I only get a list of files changed:
Changes
application\std-interview\src\main\java\com\stchome\dsms\appl\formdatasources\stdinterview\InterviewTravelHistoryListHelper.java
application\std-interview\src\main\java\com\stchome\dsms\appl\formdatasources\stdinterview\InterviewTravelHistoryHelper.java
application\std-interview\src\main\java\com\stchome\dsms\appl\formdatasources\stdinterview\InterviewTravelAndNotesHelper.java
I'm using 1.0.3so how do I turn on the other info?
-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Friday, August 18, 2006 9:19 AM
To: continuum-users@maven.apache.org
Subject: Re: Blame mechanism with SVN
It isn't really the svn blame mechanism but only the list of changes in the
build result screen with
(author, date, modified files and commit comments)
Emmanuel
Brian E. Fox a écrit :
> Actually, I mean turn on the svn blame output in continuum.
>
> -Original Message-
> From: Binil Thomas [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 18, 2006 1:57 AM
> To: continuum-users@maven.apache.org
> Subject: Re: Blame mechanism with SVN
>
> Brian,
>
> I assume that you meant the logs when you asked "How do you turn this on?".
>
> I do not remember doing anything special for turning on the logs. I think
> they are configured in the
> $CONTINUUM_HOME/apps/continuum/conf/application.xml file - look for the
> component 'Logger manager'. For my installation, this component is configured
> as:
>
>
>
> org.codehaus.plexus.logging.LoggerManager
>
> org.codehaus.plexus.logging.log4j.Log4JLoggerManager
> basic
>
>
> DEBUG
> console,rolling
>
>
> console
> DEBUG
> org.apache.log4j.ConsoleAppender
> %d [%t] %-5p %-30c{1} -
> %m%n
>
>
>
> rolling
> DEBUG
> org.apache.log4j.RollingFileAppender
> %-4r [%t] %-5p %c %x -
> %m%n
>
>
>
> file
> ${plexus.home}/logs/continuum.log
>
>
> append
> true
>
>
> maxBackupIndex
> 10
>
>
> maxFileSize
> 10MB
>
>
>
>
>
>
>
> org.apache.maven.continuum.execution.maven.m2.MavenBuilderHelper
> INFO
>
>
> org.codehaus.plexus.velocity
> WARN
>
>
> org.codehaus.plexus.mailsender.MailSender
> INFO
>
>
> JPOX
> INFO
>
>
> JPOX.Cache
> WARN
>
>
>
>
>
> I don't remeber touching these configurations.
>
> Also, in my installation, Contiuum logs to
> %CONTIUUM_HOME/apps/continuum/logs/contiuum.log. It also logs to
> %CONTIUUM_HOME%/logs/wrapper.log, although I do not know where this is
> configured at.
>
> Thanks,
> Binil
>
>
> On 8/18/06, Brian E. Fox <[EMAIL PROTECTED]> wrote:
>> How do you turn this on? I'm also using 1.0.3 and svn but haven't seen this
>> option anywhere.
>>
>> -Original Message-
>> From: Binil Thomas [mailto:[EMAIL PROTECTED]
>> Sent: Friday, August 11, 2006 9:57 AM
>> To: continuum-users@maven.apache.org
>> Subject: Re: Blame mechanism with SVN
>>
>> Emmanuel,
>>
>> I looked through the logs and found the svn command which Continuum issues
>> to get the logs. When I run that command on the CI server machine, I do get
>> proper log information.
>>
>> Here is what I get:
>>
>>> svn --non-interactive log -v -r "{2006-08-07 13:37:58 +}:HEAD"
>>> http://my.svn.server/myproject/trunk/myapp
>> --
>> --
>> r174 | one.developer | 2006-08-08 12:24:02 +0530 (Tue, 08 Aug 2006) | 1 line
>> Changed paths:
>>D /myproject/trunk/myapp/src/test/java/apackage
>> [snipped ...]
>>D /myproject/trunk/myapp/src/test/java/mypackage/an.xml
>>
>> One line of comment.
>> --
>>
Re: Blame mechanism with SVN
It isn't really the svn blame mechanism but only the list of changes in the build result screen with
(author, date, modified files and commit comments)
Emmanuel
Brian E. Fox a écrit :
Actually, I mean turn on the svn blame output in continuum.
-Original Message-
From: Binil Thomas [mailto:[EMAIL PROTECTED]
Sent: Friday, August 18, 2006 1:57 AM
To: continuum-users@maven.apache.org
Subject: Re: Blame mechanism with SVN
Brian,
I assume that you meant the logs when you asked "How do you turn this on?".
I do not remember doing anything special for turning on the logs. I think they
are configured in the $CONTINUUM_HOME/apps/continuum/conf/application.xml file
- look for the component 'Logger manager'. For my installation, this component
is configured as:
org.codehaus.plexus.logging.LoggerManager
org.codehaus.plexus.logging.log4j.Log4JLoggerManager
basic
DEBUG
console,rolling
console
DEBUG
org.apache.log4j.ConsoleAppender
%d [%t] %-5p %-30c{1} -
%m%n
rolling
DEBUG
org.apache.log4j.RollingFileAppender
%-4r [%t] %-5p %c %x - %m%n
file
${plexus.home}/logs/continuum.log
append
true
maxBackupIndex
10
maxFileSize
10MB
org.apache.maven.continuum.execution.maven.m2.MavenBuilderHelper
INFO
org.codehaus.plexus.velocity
WARN
org.codehaus.plexus.mailsender.MailSender
INFO
JPOX
INFO
JPOX.Cache
WARN
I don't remeber touching these configurations.
Also, in my installation, Contiuum logs to
%CONTIUUM_HOME/apps/continuum/logs/contiuum.log. It also logs to
%CONTIUUM_HOME%/logs/wrapper.log, although I do not know where this is
configured at.
Thanks,
Binil
On 8/18/06, Brian E. Fox <[EMAIL PROTECTED]> wrote:
How do you turn this on? I'm also using 1.0.3 and svn but haven't seen this
option anywhere.
-Original Message-
From: Binil Thomas [mailto:[EMAIL PROTECTED]
Sent: Friday, August 11, 2006 9:57 AM
To: continuum-users@maven.apache.org
Subject: Re: Blame mechanism with SVN
Emmanuel,
I looked through the logs and found the svn command which Continuum issues to
get the logs. When I run that command on the CI server machine, I do get proper
log information.
Here is what I get:
svn --non-interactive log -v -r "{2006-08-07 13:37:58 +}:HEAD"
http://my.svn.server/myproject/trunk/myapp
--
--
r174 | one.developer | 2006-08-08 12:24:02 +0530 (Tue, 08 Aug 2006) | 1 line
Changed paths:
D /myproject/trunk/myapp/src/test/java/apackage
[snipped ...]
D /myproject/trunk/myapp/src/test/java/mypackage/an.xml
One line of comment.
--
-- r180 | one.developer | 2006-08-11 11:08:35 +0530 (Fri, 11 Aug 2006)
| 4 lines Changed paths:
M /myproject/trunk/myapp/.classpath [snipped ...]
D /myproject/trunk/myapp/src/test/java/mypackage/ATest.java
A comment here.
Another comment here.
Yet another comment here.
--
--
Here is a snippet of log that might be useful.
INFO | jvm 1| 2006/08/11 18:53:09 | 2006-08-11 18:53:09,587
[Thread-2] INFO ContinuumScm - Updating project:
id: '22', name 'myapp'.
INFO | jvm 1| 2006/08/11 18:53:09 | 2006-08-11 18:53:09,602
[Thread-2] INFO ScmManager - Executing: svn
--non-interactive update
INFO | jvm 1| 2006/08/11 18:53:09 | 2006-08-11 18:53:09,602
[Thread-2] INFO ScmManager - Working directory:
D:\softwares\continuum-1.0.3\bin\win32\..\..\apps\continuum\working-directory\22
INFO | jvm 1| 2006/08/11 18:53:15 | 2006-08-11 18:53:15,103
[Thread-31] DEBUG ScmManager - U
src\test\java\my\package\File1.java
INFO | jvm 1| 2006/08/11 18:53:15 | 2006-08-11 18:53:15,103
[Thread-31] DEBUG ScmManager - D
src\test\java\my\package\File2.java
INFO | jvm 1| 2006/08/11 18:53:15 | 2006-08-11 18:53:15,103
[Thread-31] DEBUG ScmManager - Skipping non-file:
src\test\my\package\File3.java
INFO | jvm 1| 2006/08/11 18:53:15 | 2006-08-11 18:53:15,103
[Thread-31] DEBUG ScmManager - D
src\main\jav
Re: Blame mechanism with SVN
What is the language used by your svn? I guess it isn't english, right?
Emmanuel
Binil Thomas a écrit :
Hi all,
I am using Continuum 1.0.3, Maven 2.0.4 and SVN. Is there anything
special I
need to do to get the blame mechanism working? I have seen previous posts
here, and someone did reply that it is fixed in 1.0.3, but I still am not
getting it to work.
I am attaching a sample failure email I got. It currently shows the files
that are changed, but does not show who changed them.
Kindly help me configure the failure email to show the id which changed a
file.
Thanks,
Binil
Online report :
Build statistics:
State: Failed
Previous State: Failed
Started at: Mon, 7 Aug 2006 15:52:38 +0530
Finished at: Mon, 7 Aug 2006 15:52:59 +0530
Total time: 21s
Build Trigger: Forced
Exit code: 1
Building machine hostname: MY-BUILD-MACHINE
Operating system : Windows 2000(Service Pack 4)
Java version : 1.5.0_06(Sun Microsystems Inc.)
Changes
src\main\java\my\package\MyClass.java
Output:
[INFO] Scanning for projects...
[INFO]
[INFO] Building myproject
[INFO]task-segment: [clean, install, deploy]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory D:\softwares\continuum-
1.0.3\apps\continuum\working-directory\20\target
[INFO] Deleting directory D:\softwares\continuum-
1.0.3\apps\continuum\working-directory\20\target\classes
[INFO] Deleting directory D:\softwares\continuum-
1.0.3\apps\continuum\working-directory\20\target\test-classes
[INFO] [cobertura:clean {execution: clean}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 68 source files to D:\softwares\continuum-
1.0.3\apps\continuum\working-directory\20\target\classes
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
Compiling 19 source files to D:\softwares\continuum-
1.0.3\apps\continuum\working-directory\20\target\test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory: D:\softwares\continuum-
1.0.3\apps\continuum\working-directory\20\target\surefire-reports
---
T E S T S
---
[..snipped..]
Results :
Tests run: 61, Failures: 0, Errors: 3, Skipped: 0
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] There are test failures.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 19 seconds
[INFO] Finished at: Mon Aug 07 15:52:59 IST 2006
[INFO] Final Memory: 7M/20M
[INFO]
Blame mechanism with SVN
Hi all,
I am using Continuum 1.0.3, Maven 2.0.4 and SVN. Is there anything special I
need to do to get the blame mechanism working? I have seen previous posts
here, and someone did reply that it is fixed in 1.0.3, but I still am not
getting it to work.
I am attaching a sample failure email I got. It currently shows the files
that are changed, but does not show who changed them.
Kindly help me configure the failure email to show the id which changed a
file.
Thanks,
Binil
Online report :
Build statistics:
State: Failed
Previous State: Failed
Started at: Mon, 7 Aug 2006 15:52:38 +0530
Finished at: Mon, 7 Aug 2006 15:52:59 +0530
Total time: 21s
Build Trigger: Forced
Exit code: 1
Building machine hostname: MY-BUILD-MACHINE
Operating system : Windows 2000(Service Pack 4)
Java version : 1.5.0_06(Sun Microsystems Inc.)
Changes
src\main\java\my\package\MyClass.java
Output:
[INFO] Scanning for projects...
[INFO]
[INFO] Building myproject
[INFO]task-segment: [clean, install, deploy]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory D:\softwares\continuum-
1.0.3\apps\continuum\working-directory\20\target
[INFO] Deleting directory D:\softwares\continuum-
1.0.3\apps\continuum\working-directory\20\target\classes
[INFO] Deleting directory D:\softwares\continuum-
1.0.3\apps\continuum\working-directory\20\target\test-classes
[INFO] [cobertura:clean {execution: clean}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 68 source files to D:\softwares\continuum-
1.0.3\apps\continuum\working-directory\20\target\classes
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
Compiling 19 source files to D:\softwares\continuum-
1.0.3\apps\continuum\working-directory\20\target\test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory: D:\softwares\continuum-
1.0.3\apps\continuum\working-directory\20\target\surefire-reports
---
T E S T S
---
[..snipped..]
Results :
Tests run: 61, Failures: 0, Errors: 3, Skipped: 0
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] There are test failures.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 19 seconds
[INFO] Finished at: Mon Aug 07 15:52:59 IST 2006
[INFO] Final Memory: 7M/20M
[INFO]
Re: Blame mechanism - display SCM commit #, committer, date
I fixed it in continuum 1.0.3 :-) Emmanuel Chris Wall a écrit : Continuum version: 1.0.2 Os: Red Hat Enterprise Linux AS release 4 (Nahant Update 2) SVN version: 1.3.0 Language: Java -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: June 08, 2006 3:12 PM To: continuum-users@maven.apache.org Subject: Re: Blame mechanism - display SCM commit #, committer, date Normally, the date and the committer is in the changes screen. Check your logs to see if you have some parsing errors. What is your os, svn version, language used? Emmanuel Chris Wall a écrit : Right now we're just displaying the list of changes when a build breaks. How can I configure Continuum to include for each commit the #, committer, and date? We're using Subversion. Thanks. -Chris ___ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. ___ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
RE: Blame mechanism - display SCM commit #, committer, date
Continuum version: 1.0.2 Os: Red Hat Enterprise Linux AS release 4 (Nahant Update 2) SVN version: 1.3.0 Language: Java -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: June 08, 2006 3:12 PM To: continuum-users@maven.apache.org Subject: Re: Blame mechanism - display SCM commit #, committer, date Normally, the date and the committer is in the changes screen. Check your logs to see if you have some parsing errors. What is your os, svn version, language used? Emmanuel Chris Wall a écrit : > Right now we're just displaying the list of changes when a build breaks. > How can I configure Continuum to include for each commit the #, > committer, and date? We're using Subversion. > > Thanks. > > -Chris > ___ > Notice: This email message, together with any attachments, may contain > information of BEA Systems, Inc., its subsidiaries and affiliated > entities, that may be confidential, proprietary, copyrighted and/or > legally privileged, and is intended solely for the use of the individual > or entity named in this message. If you are not the intended recipient, > and have received this message in error, please immediately return this > by email and then delete it. > ___ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
Re: Blame mechanism - display SCM commit #, committer, date
Normally, the date and the committer is in the changes screen. Check your logs to see if you have some parsing errors. What is your os, svn version, language used? Emmanuel Chris Wall a écrit : Right now we're just displaying the list of changes when a build breaks. How can I configure Continuum to include for each commit the #, committer, and date? We're using Subversion. Thanks. -Chris ___ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
Blame mechanism - display SCM commit #, committer, date
Right now we're just displaying the list of changes when a build breaks. How can I configure Continuum to include for each commit the #, committer, and date? We're using Subversion. Thanks. -Chris ___ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
Re: Blame mechanism
All blame info must appears in build result report. So you can see all changes since last update and since last successful build (with dates, modified files, authors and comments). If you don't see them, it's a bug. Emmanuel Dietrich Schulten a écrit : Hi, where can I find more information about continuum's blame mechanism? What exactly does it achieve and how do I have to configure it? Regards, Dietrich
Blame mechanism
Hi, where can I find more information about continuum's blame mechanism? What exactly does it achieve and how do I have to configure it? Regards, Dietrich
Blame mechanism
Hi, where can I find more information about continuum's blame mechanism? What exactly does it achieve and how do I have to configure it? Regards, Dietrich
