[ http://jira.codehaus.org/browse/CONTINUUM-2628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching updated CONTINUUM-2628:
----------------------------------------

    Summary: Continuum uses SCM credentials provided on project add when checking out and updating working copy during project build and during release:prepare when using GIT and SSH in SCM urls  (was: Continuum uses SCM credentials provided on project add when executing update-working-copy during release:prepare if the protocol specified in the SCM urls in pom is SSH (using GIT))

Updated subject to reflect the entire affected parts.

> Continuum uses SCM credentials provided on project add when checking out and updating working copy during project build and during release:prepare when using GIT and SSH in SCM urls
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CONTINUUM-2628
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-2628
>             Project: Continuum
>          Issue Type: Bug
>          Components: Release, SCM
>    Affects Versions: 1.4.0 (Beta)
>            Reporter: Maria Odea Ching
>            Assignee: Maria Odea Ching
>             Fix For: 1.4.1 (Beta)
>
>
> In the continuum-build agent logs below, the username and password specified in the scm command {{git pull ssh://oching:PASSWORD@github.com/myprivaterepository/myproject.git}} during {{update-working-copy}} are the SCM credentials I provided during project add. 
> The {{connectionUrl}} and {{developerConnectionUrl}} specified in my POM are {{scm:git:ssh://git@github.com/myprivaterepository/myproject.git}}
> I added my project using the POM Url: {{https://github.com/myprivaterepository/myproject/raw/master/pom.xml}}
> {code}
> 2011-05-23 10:59:02,806 [btpool0-4] INFO  org.apache.continuum.distributed.transport.slave.SlaveBuildAgentTransportServer  - Preparing release
> 2011-05-23 10:59:03,622 [pool-3-thread-1] INFO  releasePhase#update-working-copy  - Updating local copy against the scm...
> 2011-05-23 10:59:03,808 [pool-3-thread-1] INFO  releasePhase#update-working-copy  - Executing: /bin/sh -c cd /Users/Deng/Checkouts/continuum-trunk/continuum-buildagent/continuum-buildagent-jetty/target/apache-continuum-buildagent-1.4.1-SNAPSHOT/data/working-directory/231 && git symbolic-ref HEAD
> 2011-05-23 10:59:03,808 [pool-3-thread-1] INFO  releasePhase#update-working-copy  - Working directory: /Users/Deng/Checkouts/continuum-trunk/continuum-buildagent/continuum-buildagent-jetty/target/apache-continuum-buildagent-1.4.1-SNAPSHOT/data/working-directory/231
> 2011-05-23 10:59:04,063 [btpool0-4] INFO  org.apache.continuum.buildagent.ContinuumBuildAgentServiceImpl  - Ping Ok
> 2011-05-23 10:59:04,102 [btpool0-4] INFO  org.apache.continuum.distributed.transport.slave.SlaveBuildAgentTransportServer  - Retrieving listener for releaseId=com.maestrodev.maestro:parent
> 2011-05-23 10:59:04,628 [pool-3-thread-1] INFO  scmManager  - Executing: /bin/sh -c cd /Users/Deng/Checkouts/continuum-trunk/continuum-buildagent/continuum-buildagent-jetty/target/apache-continuum-buildagent-1.4.1-SNAPSHOT/data/working-directory/231 && git pull ssh://oching:PASSWORD@github.com/myprivaterepository/myproject.git master
> 2011-05-23 10:59:04,630 [pool-3-thread-1] INFO  scmManager  - Working directory: /Users/Deng/Checkouts/continuum-trunk/continuum-buildagent/continuum-buildagent-jetty/target/apache-continuum-buildagent-1.4.1-SNAPSHOT/data/working-directory/231
> 2011-05-23 10:59:14,146 [btpool0-0] INFO  org.apache.continuum.buildagent.ContinuumBuildAgentServiceImpl  - Ping Ok
> 2011-05-23 10:59:14,152 [btpool0-0] INFO  org.apache.continuum.distributed.transport.slave.SlaveBuildAgentTransportServer  - Retrieving listener for releaseId=com.maestrodev.maestro:parent
> 2011-05-23 10:59:23,030 [pool-3-thread-1] WARN  scmManager  - failed to update git, return code 1
> {code}

-- 
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