Continuum

Using multiple Ant projects with Continuum and Perforce SCM - the perforce views are incorrectly created

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.0.3
  • Fix Version/s: None
  • Component/s: SCM
  • Environment:
    Windows Server 2003
    Ant 1.6.5
    Maven 2.0.4
    Continuum 1.0.3
    JDK 1.5.0_06
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

Using multiple Ant projects with Continuum and Perforce SCM - the perforce views are incorrectly created

The first client created automagically works correctly.

The second project generates a client that references the first. From the log files:

1052282 [Thread-3] INFO org.apache.maven.continuum.scm.ContinuumScm - Checking out project: 'GUR - Crc Generator', id: '2' to 'C:\continuum-1.0.3\bin\win32\..\..\apps\continuum\working-directory\2'.
1052282 [Thread-3] INFO org.apache.maven.scm.manager.ScmManager - Checkout working directory: C:\continuum-1.0.3\bin\win32\..\..\apps\continuum\working-directory\2
1052282 [Thread-3] INFO org.apache.maven.scm.manager.ScmManager - Executing: p4 client -i
1052282 [Thread-3] DEBUG org.apache.maven.scm.manager.ScmManager - Updating clientspec:
Client: webguest-sepoe-build2-MavenSCM-C:\continuum-1.0.3\apps\continuum\working-directory\1
Root: C:\continuum-1.0.3\bin\win32\..\..\apps\continuum\working-directory\2
Owner: webguest
View:
//p4-tss/gur/Development/CrcGenerator/1.0/... //webguest-sepoe-build2-MavenSCM-C:\continuum-1.0.3\apps\continuum\working-directory\1/...
Description:
Created by maven-scm-provider-perforce

This client that has been generated should be references working-directory\2/... not 1

Adding a third project shows that it also references the first "client":

1080922 [Thread-3] INFO org.apache.maven.continuum.scm.ContinuumScm - Checking out project: 'GUR - Crc Local', id: '3' to 'C:\continuum-1.0.3\bin\win32\..\..\apps\continuum\working-directory\3'.
1080922 [Thread-3] INFO org.apache.maven.scm.manager.ScmManager - Checkout working directory: C:\continuum-1.0.3\bin\win32\..\..\apps\continuum\working-directory\3
1080922 [Thread-3] INFO org.apache.maven.scm.manager.ScmManager - Executing: p4 client -i
1080922 [Thread-3] DEBUG org.apache.maven.scm.manager.ScmManager - Updating clientspec:
Client: webguest-sepoe-build2-MavenSCM-C:\continuum-1.0.3\apps\continuum\working-directory\1
Root: C:\continuum-1.0.3\bin\win32\..\..\apps\continuum\working-directory\3
Owner: webguest
View:
//p4-tss/gur/Development/CrcLocalApi/1.0/... //webguest-sepoe-build2-MavenSCM-C:\continuum-1.0.3\apps\continuum\working-directory\1/...
Description:
Created by maven-scm-provider-perforce

I haven't yet dug into the code to determine where the client view gets set, but that appears to be where the mistake is being made.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Joseph Heck added a comment -

Ant appears to be inconsequential to this issue. I've added Maven2 projects to the build system and end with the same result.

I'm looking deeper into org.apache.maven.continuum.scm.ContinuumScm to try and determine where this problem is occuring.

Show
Joseph Heck added a comment - Ant appears to be inconsequential to this issue. I've added Maven2 projects to the build system and end with the same result. I'm looking deeper into org.apache.maven.continuum.scm.ContinuumScm to try and determine where this problem is occuring.
Hide
Permalink
Bob Arnott added a comment -

I'm seeing the same problem, I have a number of Ant based projects, stored in Perforce. Not only does the SCM reference both projects that I have added so far, it references the entire contents of each project every time a scheduled build happens. This means that it builds both projects regardless of any changes made.

My P4 SCM URLs are

scm:perforce:perforce.mycompany.com:1668://depot/scratch/boba/Project1/...
scm:perforce:perforce.mycompany.com:1668://depot/scratch/boba/Project2/...

And in the changes window when viewing the results of a build on Project2 I see:

//depot/scratch/boba/Project1/libs/ant/ant-1.7.0.jar
//depot/scratch/boba/Project1/libs/ant/ant-testutil-1.7.0.jar
//depot/scratch/boba/Project1/libs/junit/junit-3.8.2.jar
...
//depot/scratch/boba/Project2/build.properties
//depot/scratch/boba/Project2/build.xml
//depot/scratch/boba/Project2/libs/Tomcat-5.5.x/catalina-ant.jar
...

Conversely when I look at the results for a build of Project1 I see:

//depot/scratch/boba/Project2/build.properties
//depot/scratch/boba/Project2/build.xml
//depot/scratch/boba/Project2/libs/Tomcat-5.5.x/catalina-ant.jar
...
//depot/scratch/boba/Project1/libs/ant/ant-1.7.0.jar
//depot/scratch/boba/Project1/libs/ant/ant-testutil-1.7.0.jar
//depot/scratch/boba/Project1/libs/junit/junit-3.8.2.jar
...

I have had problems with Perforce and CruiseControl in the past where it wouldn't detect changes that had been made and thus wouldn't trigger a build. So I don't know if this is P4 being a pile of steaming poo, or if it's a proper Continuum SCM issue.

Show
Bob Arnott added a comment - I'm seeing the same problem, I have a number of Ant based projects, stored in Perforce. Not only does the SCM reference both projects that I have added so far, it references the entire contents of each project every time a scheduled build happens. This means that it builds both projects regardless of any changes made. My P4 SCM URLs are scm:perforce:perforce.mycompany.com:1668://depot/scratch/boba/Project1/... scm:perforce:perforce.mycompany.com:1668://depot/scratch/boba/Project2/... And in the changes window when viewing the results of a build on Project2 I see: //depot/scratch/boba/Project1/libs/ant/ant-1.7.0.jar //depot/scratch/boba/Project1/libs/ant/ant-testutil-1.7.0.jar //depot/scratch/boba/Project1/libs/junit/junit-3.8.2.jar ... //depot/scratch/boba/Project2/build.properties //depot/scratch/boba/Project2/build.xml //depot/scratch/boba/Project2/libs/Tomcat-5.5.x/catalina-ant.jar ... Conversely when I look at the results for a build of Project1 I see: //depot/scratch/boba/Project2/build.properties //depot/scratch/boba/Project2/build.xml //depot/scratch/boba/Project2/libs/Tomcat-5.5.x/catalina-ant.jar ... //depot/scratch/boba/Project1/libs/ant/ant-1.7.0.jar //depot/scratch/boba/Project1/libs/ant/ant-testutil-1.7.0.jar //depot/scratch/boba/Project1/libs/junit/junit-3.8.2.jar ... I have had problems with Perforce and CruiseControl in the past where it wouldn't detect changes that had been made and thus wouldn't trigger a build. So I don't know if this is P4 being a pile of steaming poo, or if it's a proper Continuum SCM issue.
Hide
Permalink
Joseph Heck added a comment -

Doing more digging into the logs and code, here's what I've found:

When the Continuum server slips from one project to another, it uses the built in "SCM.checkout" command to check out the indicated project to a working directory. In the background, the org.apache.maven.scm setup attempts to re-use the original client, so it updates the client - resulting in all of the previous project being "removed" and then the new project "added". When the client is updated as such, it "appears" to have changes, and therefore always invokes a build.

This change appears to be related to SCM-113 (http://jira.codehaus.org/browse/SCM-113). At the tail end of that particular bug, there is commentary talking about the impact to this specific issue. The resulting bug that was filed in Continuum was CONTINUUM-584 (http://jira.codehaus.org/browse/CONTINUUM-584), which is reported as fixed. (commit #376470 according to JIRA).

That change IS in place, but it doesn't necessarily appear to be having the desired effect. The result is that the single client spec gets updated constantly, but new client specs aren't getting created for each build. This is, unfortunately, exactly how the SCM undersystem is built.

Show
Joseph Heck added a comment - Doing more digging into the logs and code, here's what I've found: When the Continuum server slips from one project to another, it uses the built in "SCM.checkout" command to check out the indicated project to a working directory. In the background, the org.apache.maven.scm setup attempts to re-use the original client, so it updates the client - resulting in all of the previous project being "removed" and then the new project "added". When the client is updated as such, it "appears" to have changes, and therefore always invokes a build. This change appears to be related to SCM-113 ( http://jira.codehaus.org/browse/SCM-113 ). At the tail end of that particular bug, there is commentary talking about the impact to this specific issue. The resulting bug that was filed in Continuum was CONTINUUM-584 ( http://jira.codehaus.org/browse/CONTINUUM-584 ), which is reported as fixed. (commit #376470 according to JIRA). That change IS in place, but it doesn't necessarily appear to be having the desired effect. The result is that the single client spec gets updated constantly, but new client specs aren't getting created for each build. This is, unfortunately, exactly how the SCM undersystem is built.
Hide
Permalink
Spencer White added a comment -

I am having this issue as well. I have tried:
1) continuum-plexus-runtime-1.1-alpha-2-bin.tar.gz
2) continuum-plexus-runtime-1.1-beta-1-bin.tar.gz
3) continuum-plexus-runtime-1.1-beta-2-bin.tar.gz
4) apache-continuum-1.1-beta-3.tar.gz
5) apache-continuum-1.1-beta-4.tar.bz2
6) continuum-1.0.3-bin.tar.bz2

I have the same issue. When I look at the client specs that are in the continuum logs, continuum is overwriting the client spec on each run and still updates every file, so it performs a build every time it runs.

I see a few references to others having the same problem. Has it been fixed and I don't know how to implement the fix?

Thanks.

--Spencer

Show
Spencer White added a comment - I am having this issue as well. I have tried: 1) continuum-plexus-runtime-1.1-alpha-2-bin.tar.gz 2) continuum-plexus-runtime-1.1-beta-1-bin.tar.gz 3) continuum-plexus-runtime-1.1-beta-2-bin.tar.gz 4) apache-continuum-1.1-beta-3.tar.gz 5) apache-continuum-1.1-beta-4.tar.bz2 6) continuum-1.0.3-bin.tar.bz2 I have the same issue. When I look at the client specs that are in the continuum logs, continuum is overwriting the client spec on each run and still updates every file, so it performs a build every time it runs. I see a few references to others having the same problem. Has it been fixed and I don't know how to implement the fix? Thanks. --Spencer

People

  • Assignee:
    Unassigned
    Reporter:
    Joseph Heck
Vote (2)
Watch (2)

Dates

  • Created:
    Updated: