continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Firass Shehadeh (JIRA)" <>
Subject [jira] Commented: (CONTINUUM-1565) continuum does not see update files via Perforce scm plugin
Date Thu, 29 May 2008 14:41:21 GMT


Firass Shehadeh commented on CONTINUUM-1565:

I am seeing the same problem using a CSV repository. When I check the "Build Fresh" check
box in the "Add/Edit Build Definition" screen, then Continuum will not automatically build
my project because it thinks that there are no changes. 

The workaround that I have been using was tp un-check the box. However, every once in a while,
the CVS working directory gets out of sync, and the I have to force a clean checkout to force
the server to detect new changes, and this requires me to check the box, do a build, and then
un-check the box again.

> continuum does not see update files via Perforce scm plugin
> -----------------------------------------------------------
>                 Key: CONTINUUM-1565
>                 URL:
>             Project: Continuum
>          Issue Type: Bug
>          Components: SCM
>    Affects Versions: 1.1-beta-4
>         Environment: linux, Perforce Server 2005.2.PATCH/100601, maven 2.0.7,
jdk 1.6.0_03
>            Reporter: Spencer White
>             Fix For: 1.x
> BuildController does not see changes and therefor does not do a build. Here is how I
> 1. cd /project/dir
> 2. find ./ -type f -exec md5sum {} \; > 2.old
> 3. check in changes to perforce from another client
> 4. wait for Continuum to do run it's scheduled task to update code
> 5. Continuum:
> 346298228 [pool-1-thread-1] INFO  org.apache.maven.continuum.buildcontroller.BuildController:default
 - Merging SCM results
> 346298254 [pool-1-thread-1] INFO  org.apache.maven.continuum.buildcontroller.BuildController:default
 - The project was not built because no changes were detected in sources since the last build.
> 346298255 [pool-1-thread-1] INFO  org.apache.maven.continuum.buildcontroller.BuildController:default
 - No changes, not building
> 6. find ./ -type f -exec md5sum {} \; >
> 7. diff 2.old
> 28c27
> < d408dc1aab6914b85e3bd2e1ae609368  ./src/main/java/com/visto/apps/client/
> ---
> > 79dfa098c212744ffec226a8126bb3f5  ./src/main/java/com/visto/apps/client/
> was the file that I had changed and checked into perforce.

> In Continuum 1.0.3 this project worked fine but it looks like maven-scm used p4 sync
to update files. Then I had to add another project on the same perforce server and had to
upgrade to 1.1-beta-4.
> This may have something to do with the maven-scm plugin possibly?
> Thanks.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message