[jira] Created: (CONTINUUM-415) cvs update log shows all updates, not just relevant updates
cvs update log shows all updates, not just relevant updates --- Key: CONTINUUM-415 URL: http://jira.codehaus.org/browse/CONTINUUM-415 Project: Continuum Type: Bug Components: continuum-core Versions: 1.0 Environment: WinXP Client: Concurrent Versions System (CVSNT) 2.5.02 (Servalan) Build 2115 (client/server) Server: Concurrent Versions System (CVSNT) 2.0.34 (client/server) Reporter: Brian Ewins To reproduce, perform a build on a project which uses CVS. Take a look at the results for the build What I see is the list of files changed in the most recent update, followed by the author and comment for /every/ commit on those files /ever/. What I expected to see was (at best) only changes since the last build, or (at least) only recent changes, say in the last day or two. I've traced this one down a bit, the cause is quite convoluted; the code producing the log is making an incorrect assumption about the ScmResults created on updates. Here's the call sequence that's messing up as far as I can tell (from browsing svn and correlating with the log messages I see): DefaultContinuum.buildProject(various) -..after a couple of steps..- DefaultContinuumScm.updateProject(project) - [ScmResult] result = convertScmResult( scmManager.getProviderByRepository( repository ).update( repository, fileSet, tag ) ) - [CvsScmProvider].update(repository, fileSet, tag) - [AbstractUpdateCommand].execute( repository.getProviderRepository(), fileSet, parameters ) - (ChangeLogScmResult) [AbstractChangeLogCommand].executeCommand( repository, fileSet, parameters ); - [CvsChangeLogCommand].executeCommand(repository, fileSet, null, null, 0, branch) This then calls cvs log with no date limiting parameters, so the ScmResult for the update contains the full log, although it is trimmed to just the files that changed. then later on, when asked to produce the build log: DefaultContinuum.getChangesSinceLastSuccess(projectId, buildId) - changes.addAll( buildResult.getScmResult().getChanges() ); This adds all the changes recorded in that build result, which the previous trace shows are actually all changes, ever. This set of changes isn't then filtered by date. From the looks of 'getChangesSinceLastSuccess' its supposed to provide a list of all changes from build 'buildId' up to the current one. The assumption in that method appears to be that each buildResult contains only appropriate changes. However, since it contains /all/ changes, I'd expect that the situation is much worse: multiple changes to a file since the last build will mean we get multiple copies of /all/ changes to that file dumped into the log. There's some kind of logical disconnect here. I think what's missing is that the call to 'scmManager.getProviderByRepository( repository ).update( repository, fileSet, tag ) ' should actually be passing in the timestamp of the previous build, so that we can retrieve just changes since that build: that way the assumption in 'getChangesSinceLastSuccess' is correct. - that the changes from multiple builds can just be appended together. If I've diagnosed this wrong, then it means that whatever's meant to filter down the changes to just those since the last build isn't working. I couldn't find any code that was actually attempting to do that, though. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-413) build reported as successful on win xp even when maven 1 build fails
[ http://jira.codehaus.org/browse/CONTINUUM-413?page=comments#action_49824 ] Alan Cabrera commented on CONTINUUM-413: I also get this problem w/ Windows Server 2003 build reported as successful on win xp even when maven 1 build fails Key: CONTINUUM-413 URL: http://jira.codehaus.org/browse/CONTINUUM-413 Project: Continuum Type: Bug Versions: 1.0 Environment: Maven 1.0.2 Java 1.5 Win XP SP2 Continuum 1.0 Reporter: Zach B Continuum always reports a successful build even when Maven reports a build failure. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-416) A button I could click on the login page to remember me and automatically log me in next time
A button I could click on the login page to remember me and automatically log me in next time - Key: CONTINUUM-416 URL: http://jira.codehaus.org/browse/CONTINUUM-416 Project: Continuum Type: Wish Components: continuum-web Versions: 1.0 Reporter: David Blevins A button I could click on the login page to remember me and automatically log me in next time. Something similar to JIRA or Confluence. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[continuum build - SKIPPED - checkout] Thu Nov 3 01:30:00 GMT 2005
ci_continuum.sh already running... exiting continuu 23303 23300 0 01:30:01 ? 0:00 /bin/sh /export/home/continuum/ci_continuum.sh checkout
[jira] Commented: (CONTINUUM-372) When building ServiceMix, the continuum web-interface displays a successful status even though the result is build failed. It even emails a successful state.
[ http://jira.codehaus.org/browse/CONTINUUM-372?page=comments#action_49858 ] Allan Ramirez commented on CONTINUUM-372: - Hi Emmanuel, We've added exit /B errorlevel at the last line of maven.bat, But the web interface still displays a successful status. When building ServiceMix, the continuum web-interface displays a successful status even though the result is build failed. It even emails a successful state. Key: CONTINUUM-372 URL: http://jira.codehaus.org/browse/CONTINUUM-372 Project: Continuum Type: Bug Versions: 1.0 Reporter: Johnny R. Ruiz III The state is successfule but the result is failed. Here is the result in continuum. -- __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0.2 build:start: clean:clean: init: [echo] init basedir=C:\JApps\continuum-1.0\apps\continuum\working-directory\6 jar:install: multiproject:projects-init: [echo] Gathering project list Starting the reactor... Our processing order: ServiceMix :: JBI ServiceMix :: Core ServiceMix :: Components ServiceMix :: Assembly ServiceMix :: JAXWS + | Gathering project list ServiceMix :: JBI | Memory: 5M/7M + + | Gathering project list ServiceMix :: Core | Memory: 5M/7M + + | Gathering project list ServiceMix :: Components | Memory: 5M/7M + + | Gathering project list ServiceMix :: Assembly | Memory: 5M/7M + + | Gathering project list ServiceMix :: JAXWS | Memory: 5M/7M + Starting the reactor... Our processing order: ServiceMix :: JBI ServiceMix :: Core ServiceMix :: Components ServiceMix :: Assembly ServiceMix :: JAXWS + | Executing jar:install ServiceMix :: JBI | Memory: 5M/7M + Attempting to download geronimo-spec-activation-1.0.2-rc4.jar. Error retrieving artifact from [http://dist.codehaus.org/geronimo-spec/jars/geronimo-spec-activation-1.0.2-rc4.jar]: java.net.UnknownHostException: dist.codehaus.org Error retrieving artifact from [http://www.ibiblio.org/maven/geronimo-spec/jars/geronimo-spec-activation-1.0.2-rc4.jar]: java.net.UnknownHostException: www.ibiblio.org BUILD FAILED File.. C:\Documents and Settings\Jontri\.maven\cache\maven-multiproject-plugin-1.3.1\plugin.jelly Element... maven:reactor Line.. 217 Column 9 The build cannot continue because of the following unsatisfied dependency: geronimo-spec-activation-1.0.2-rc4.jar Error retrieving artifact from [http://cvs.apache.org/repository/geronimo-spec/jars/geronimo-spec-activation-1.0.2-rc4.jar]: java.net.UnknownHostException: cvs.apache.org WARNING: Failed to download geronimo-spec-activation-1.0.2-rc4.jar. Total time: 31 seconds Finished at: Thu Oct 27 14:38:26 CST 2005 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-419) Can't click to see the latest build results from the main page
Can't click to see the latest build results from the main page -- Key: CONTINUUM-419 URL: http://jira.codehaus.org/browse/CONTINUUM-419 Project: Continuum Type: Improvement Components: continuum-web Versions: 1.0 Reporter: David Blevins Priority: Trivial When you are at the projects page (Summary.vm/fid/continuumProject) it's really annoying you can't just click somewhere and see the latest build results. You have to click Build History then the top results item, which is a big of traveling. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-419) Can't click to see the latest build results from the main page
[ http://jira.codehaus.org/browse/CONTINUUM-419?page=comments#action_49862 ] Brett Porter commented on CONTINUUM-419: the original designed called for the build number to be linked - would that be ok? Can't click to see the latest build results from the main page -- Key: CONTINUUM-419 URL: http://jira.codehaus.org/browse/CONTINUUM-419 Project: Continuum Type: Improvement Components: continuum-web Versions: 1.0 Reporter: David Blevins Priority: Trivial When you are at the projects page (Summary.vm/fid/continuumProject) it's really annoying you can't just click somewhere and see the latest build results. You have to click Build History then the top results item, which is a big of traveling. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-420) Can't go directly to the Builds screen to view build history when at a results page
Can't go directly to the Builds screen to view build history when at a results page - Key: CONTINUUM-420 URL: http://jira.codehaus.org/browse/CONTINUUM-420 Project: Continuum Type: Improvement Components: continuum-web Versions: 1.0 Reporter: David Blevins Priority: Trivial It's really odd as the build results page takes over the 'Build' tab. It's fine if you clicked on the results link *from* the build history page, then you can just hit the browser back button (which is still mildly annoying). But if you clicked to the results page from a build email or something you are a few clever clicks away from getting that Builds tab to list the history again. You have to click on Info or Working Copy then click to return to the Builds tab which will now be the history page rather than the results you were looking at. Very strange. Consider a Results tab that could be a fourth tab on the top. Or a Build History link inside the results page. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-419) Can't click to see the latest build results from the main page
[ http://jira.codehaus.org/browse/CONTINUUM-419?page=comments#action_49865 ] David Blevins commented on CONTINUUM-419: - Super. I'd want to use if for In progress builds too. Can't click to see the latest build results from the main page -- Key: CONTINUUM-419 URL: http://jira.codehaus.org/browse/CONTINUUM-419 Project: Continuum Type: Improvement Components: continuum-web Versions: 1.0 Reporter: David Blevins Priority: Trivial When you are at the projects page (Summary.vm/fid/continuumProject) it's really annoying you can't just click somewhere and see the latest build results. You have to click Build History then the top results item, which is a big of traveling. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
