Continuum

notification emails missing svn information

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.0.3
  • Fix Version/s: 1.1-alpha-2
  • Component/s: SCM
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    1

Description

I'm using 1.0.3 and svn 1.3.2. 99% of the time, the notifications do not list the developer or the commit message. I just get a list of changed files. I have seen it in the past occasionally but almost always the info isn't there. This includes times when there was only 1 commit since the last build.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Mattias Andersson added a comment -

I see the same behaviour with CVS as SCM provider. Only a list of files changed and no developer or commit message (this worked fine in 1.0.2). See the exampel below. It's the same in the build result view (See attached picture).

Online report : http://sorken-wm2:8080/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/11/buildId/999
Build statistics:
State: Ok
Previous State: Building
Started at: fr, 2006-08-18 01:19:51 +0200
Finished at: fr, 2006-08-18 02:14:54 +0200
Total time: 55m 2s
Build Trigger: Schedule
Exit code: 0
Building machine hostname: sorken-wm2
Operating system : Windows 2003(Service Pack 1)
Java version : 1.4.2_10(Sun Microsystems Inc.)

Changes
scripts/Database/factorydata/CAT_CUSTOMER_GROUP.dat
scripts/Database/factorydata/SYS_SUBSYSTEM_ROLE_ACCESS.dat
scripts/Database/factorydata/SYS_USER_GROUPS.dat
...
....

Show
Mattias Andersson added a comment - I see the same behaviour with CVS as SCM provider. Only a list of files changed and no developer or commit message (this worked fine in 1.0.2). See the exampel below. It's the same in the build result view (See attached picture). Online report : http://sorken-wm2:8080/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/11/buildId/999 Build statistics: State: Ok Previous State: Building Started at: fr, 2006-08-18 01:19:51 +0200 Finished at: fr, 2006-08-18 02:14:54 +0200 Total time: 55m 2s Build Trigger: Schedule Exit code: 0 Building machine hostname: sorken-wm2 Operating system : Windows 2003(Service Pack 1) Java version : 1.4.2_10(Sun Microsystems Inc.) Changes scripts/Database/factorydata/CAT_CUSTOMER_GROUP.dat scripts/Database/factorydata/SYS_SUBSYSTEM_ROLE_ACCESS.dat scripts/Database/factorydata/SYS_USER_GROUPS.dat ... ....
Hide
Permalink
David Roussel added a comment -

I get the same problem with clearcase.

Show
David Roussel added a comment - I get the same problem with clearcase.
Hide
Permalink
Javier Gonzalez added a comment -

Happens the same to me (using Continuum 1.0.3 and Subversion 1.4.2)
Actually, I've never been lucky enough to see the developer name/commit message... tried 1 commit, multiple ones, forced builds, automatic ones... it just doesn't work

Show
Javier Gonzalez added a comment - Happens the same to me (using Continuum 1.0.3 and Subversion 1.4.2) Actually, I've never been lucky enough to see the developer name/commit message... tried 1 commit, multiple ones, forced builds, automatic ones... it just doesn't work
Hide
Permalink
Andre Ranvik added a comment -

I experienced the same problem - and I believe the solution was found... At least it worked for us.

This WAS our invalid authorization.conf:

[groups]
win-dev = OUR_DOMAIN_NAME\t222222, OUR_DOMAIN_NAME\t333333

[/]

  • =
    @win-dev = rw

_______________________________________________

This IS our VALID authorization.conf:

[groups]
win-dev = OUR_DOMAIN_NAME\t222222, t222222, OUR_DOMAIN_NAME\t333333, t333333

[/]

  • =
    @win-dev = rw
    _______________________________________________
    The difference is, as you can see, that we added the users without the domain name as well as with the domain name. Why this is required is beyond me... - but it works!

The authorization.conf file is the file describing how Apache authorizes the user. Our Apache httpd.conf file contains this:
<Location /svn/repos>
DAV svn
SVNPath "F:/svnrepos"
AuthType Basic
AuthName "Subversion repository"
AuthUserFile "F:/svnrepos/conf/users.conf"
AuthAuthoritative Off
AuthName "Subversion Authentication"
AuthType SSPI
SSPIAuth On
SSPIAuthoritative Off
SSPIDomain somedome.name.org
SSPIOfferBasic On
AuthzSVNAccessFile "F:/svnrepos/conf/authorization.conf"
Require valid-user
</Location>

Show
Andre Ranvik added a comment - I experienced the same problem - and I believe the solution was found... At least it worked for us. This WAS our invalid authorization.conf: [groups] win-dev = OUR_DOMAIN_NAME\t222222, OUR_DOMAIN_NAME\t333333 [/]
  • = @win-dev = rw
_______________________________________________ This IS our VALID authorization.conf: [groups] win-dev = OUR_DOMAIN_NAME\t222222, t222222, OUR_DOMAIN_NAME\t333333, t333333 [/]
  • = @win-dev = rw _______________________________________________ The difference is, as you can see, that we added the users without the domain name as well as with the domain name. Why this is required is beyond me... - but it works!
The authorization.conf file is the file describing how Apache authorizes the user. Our Apache httpd.conf file contains this: <Location /svn/repos> DAV svn SVNPath "F:/svnrepos" AuthType Basic AuthName "Subversion repository" AuthUserFile "F:/svnrepos/conf/users.conf" AuthAuthoritative Off AuthName "Subversion Authentication" AuthType SSPI SSPIAuth On SSPIAuthoritative Off SSPIDomain somedome.name.org SSPIOfferBasic On AuthzSVNAccessFile "F:/svnrepos/conf/authorization.conf" Require valid-user </Location>
Hide
Permalink
Doug Tanner added a comment -

I too am running 1.0.3 with the same problem. Will the above work if you are not using a users or authorization file?

Show
Doug Tanner added a comment - I too am running 1.0.3 with the same problem. Will the above work if you are not using a users or authorization file?

People

Vote (1)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.