You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Rohan Holt (JIRA)" <ji...@codehaus.org> on 2008/11/06 18:50:51 UTC
[jira] Created: (CONTINUUM-1967) the action
action#update-working-directory-from-scm does not update the working
directory when mercurial is the scm being used.
the action action#update-working-directory-from-scm does not update the working directory when mercurial is the scm being used.
-------------------------------------------------------------------------------------------------------------------------------
Key: CONTINUUM-1967
URL: http://jira.codehaus.org/browse/CONTINUUM-1967
Project: Continuum
Issue Type: Bug
Affects Versions: 1.2.2
Environment: Linux, tomcat 5.5.27, continuum 1.2.2.
Reporter: Rohan Holt
After some recent changes were made to one of our projects, I performed a continuum build of the project expecting to see the new changes. The changes presented by the "SCM Changes" section of the build results screen confirmed changes existed in the mercurial repository ( local ) however, the required changes did not appear in the deployed application ( deployment is part of the build process ).
Looking in the logs showed that none of the mercurial commands executed ever updated the working directory with the latest changes.
I am not certain where, but I would expect that a "hg update" appear somewhere in this list of commands executed by continuum..Otherwise all we have is another build the same as the last.
2008-11-06 17:38:56,623 [pool-1-thread-1] INFO buildController - Updating working dir
2008-11-06 17:38:56,623 [pool-1-thread-1] INFO buildController - Performing action check-working-directory
2008-11-06 17:38:56,647 [pool-1-thread-1] INFO buildController - Performing action update-working-directory-from-scm
2008-11-06 17:38:56,947 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updating project: Release 1.0 patches', id: '7' to '/u01/app/apache-continuum-1.2.2/target/working-directory/7' with branch/tag release_1_0_patches.
2008-11-06 17:38:56,948 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - EXECUTING: /bin/sh -c cd /u01/app/apache-continuum-1.2.2/target/working-directory/7 && hg pull -r release_1_0_patches
2008-11-06 17:38:58,560 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - EXECUTING: /bin/sh -c cd /u01/app/apache-continuum-1.2.2/target/working-directory/7 && hg id
2008-11-06 17:38:58,959 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - EXECUTING: /bin/sh -c cd /u01/app/apache-continuum-1.2.2/target/working-directory/7 && hg diff -r -1
2008-11-06 17:38:59,443 [pool-1-thread-1] INFO buildController - Merging SCM results
2008-11-06 17:38:59,492 [pool-1-thread-1] INFO buildController - AlwaysBuild configured, building
2008-11-06 17:38:59,493 [pool-1-thread-1] INFO buildController - Performing action update-project-from-working-directory
2008-11-06 17:38:59,527 [pool-1-thread-1] INFO action#update-project-from-working-directory - Updating project 'Release 1.0 patches' from checkout.
2008-11-06 17:38:59,598 [pool-1-thread-1] INFO buildController - Performing action execute-builder
--
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-1967) the action
action#update-working-directory-from-scm does not update the working
directory when mercurial is the scm being used.
Posted by "Ben Fortuna (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=245782#action_245782 ]
Ben Fortuna commented on CONTINUUM-1967:
----------------------------------------
Actually it's still broken with 1.7.1. Really this bug excludes continuum from the race wrt DVCS..
> the action action#update-working-directory-from-scm does not update the working directory when mercurial is the scm being used.
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: CONTINUUM-1967
> URL: http://jira.codehaus.org/browse/CONTINUUM-1967
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.2.2
> Environment: Linux, tomcat 5.5.27, continuum 1.2.2.
> Reporter: Rohan Holt
> Fix For: Backlog
>
>
> After some recent changes were made to one of our projects, I performed a continuum build of the project expecting to see the new changes. The changes presented by the "SCM Changes" section of the build results screen confirmed changes existed in the mercurial repository ( local ) however, the required changes did not appear in the deployed application ( deployment is part of the build process ).
> Looking in the logs showed that none of the mercurial commands executed ever updated the working directory with the latest changes.
> I am not certain where, but I would expect that a "hg update" appear somewhere in this list of commands executed by continuum..Otherwise all we have is another build the same as the last.
> 2008-11-06 17:38:56,623 [pool-1-thread-1] INFO buildController - Updating working dir
> 2008-11-06 17:38:56,623 [pool-1-thread-1] INFO buildController - Performing action check-working-directory
> 2008-11-06 17:38:56,647 [pool-1-thread-1] INFO buildController - Performing action update-working-directory-from-scm
> 2008-11-06 17:38:56,947 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updating project: Release 1.0 patches', id: '7' to '/u01/app/apache-continuum-1.2.2/target/working-directory/7' with branch/tag release_1_0_patches.
> 2008-11-06 17:38:56,948 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - EXECUTING: /bin/sh -c cd /u01/app/apache-continuum-1.2.2/target/working-directory/7 && hg pull -r release_1_0_patches
> 2008-11-06 17:38:58,560 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - EXECUTING: /bin/sh -c cd /u01/app/apache-continuum-1.2.2/target/working-directory/7 && hg id
> 2008-11-06 17:38:58,959 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - EXECUTING: /bin/sh -c cd /u01/app/apache-continuum-1.2.2/target/working-directory/7 && hg diff -r -1
> 2008-11-06 17:38:59,443 [pool-1-thread-1] INFO buildController - Merging SCM results
> 2008-11-06 17:38:59,492 [pool-1-thread-1] INFO buildController - AlwaysBuild configured, building
> 2008-11-06 17:38:59,493 [pool-1-thread-1] INFO buildController - Performing action update-project-from-working-directory
> 2008-11-06 17:38:59,527 [pool-1-thread-1] INFO action#update-project-from-working-directory - Updating project 'Release 1.0 patches' from checkout.
> 2008-11-06 17:38:59,598 [pool-1-thread-1] INFO buildController - Performing action execute-builder
--
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] Updated: (CONTINUUM-1967) the action
action#update-working-directory-from-scm does not update the working
directory when mercurial is the scm being used.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated CONTINUUM-1967:
------------------------------------
Fix Version/s: 1.x
> the action action#update-working-directory-from-scm does not update the working directory when mercurial is the scm being used.
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: CONTINUUM-1967
> URL: http://jira.codehaus.org/browse/CONTINUUM-1967
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.2.2
> Environment: Linux, tomcat 5.5.27, continuum 1.2.2.
> Reporter: Rohan Holt
> Fix For: 1.x
>
>
> After some recent changes were made to one of our projects, I performed a continuum build of the project expecting to see the new changes. The changes presented by the "SCM Changes" section of the build results screen confirmed changes existed in the mercurial repository ( local ) however, the required changes did not appear in the deployed application ( deployment is part of the build process ).
> Looking in the logs showed that none of the mercurial commands executed ever updated the working directory with the latest changes.
> I am not certain where, but I would expect that a "hg update" appear somewhere in this list of commands executed by continuum..Otherwise all we have is another build the same as the last.
> 2008-11-06 17:38:56,623 [pool-1-thread-1] INFO buildController - Updating working dir
> 2008-11-06 17:38:56,623 [pool-1-thread-1] INFO buildController - Performing action check-working-directory
> 2008-11-06 17:38:56,647 [pool-1-thread-1] INFO buildController - Performing action update-working-directory-from-scm
> 2008-11-06 17:38:56,947 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updating project: Release 1.0 patches', id: '7' to '/u01/app/apache-continuum-1.2.2/target/working-directory/7' with branch/tag release_1_0_patches.
> 2008-11-06 17:38:56,948 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - EXECUTING: /bin/sh -c cd /u01/app/apache-continuum-1.2.2/target/working-directory/7 && hg pull -r release_1_0_patches
> 2008-11-06 17:38:58,560 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - EXECUTING: /bin/sh -c cd /u01/app/apache-continuum-1.2.2/target/working-directory/7 && hg id
> 2008-11-06 17:38:58,959 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - EXECUTING: /bin/sh -c cd /u01/app/apache-continuum-1.2.2/target/working-directory/7 && hg diff -r -1
> 2008-11-06 17:38:59,443 [pool-1-thread-1] INFO buildController - Merging SCM results
> 2008-11-06 17:38:59,492 [pool-1-thread-1] INFO buildController - AlwaysBuild configured, building
> 2008-11-06 17:38:59,493 [pool-1-thread-1] INFO buildController - Performing action update-project-from-working-directory
> 2008-11-06 17:38:59,527 [pool-1-thread-1] INFO action#update-project-from-working-directory - Updating project 'Release 1.0 patches' from checkout.
> 2008-11-06 17:38:59,598 [pool-1-thread-1] INFO buildController - Performing action execute-builder
--
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-1967) the action
action#update-working-directory-from-scm does not update the working
directory when mercurial is the scm being used.
Posted by "Ben Fortuna (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=245768#action_245768 ]
Ben Fortuna commented on CONTINUUM-1967:
----------------------------------------
I had this same problem using Mercurial 1.4.3, but an upgrade to 1.7.1 appears to have fixed the problem.
> the action action#update-working-directory-from-scm does not update the working directory when mercurial is the scm being used.
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: CONTINUUM-1967
> URL: http://jira.codehaus.org/browse/CONTINUUM-1967
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.2.2
> Environment: Linux, tomcat 5.5.27, continuum 1.2.2.
> Reporter: Rohan Holt
> Fix For: Backlog
>
>
> After some recent changes were made to one of our projects, I performed a continuum build of the project expecting to see the new changes. The changes presented by the "SCM Changes" section of the build results screen confirmed changes existed in the mercurial repository ( local ) however, the required changes did not appear in the deployed application ( deployment is part of the build process ).
> Looking in the logs showed that none of the mercurial commands executed ever updated the working directory with the latest changes.
> I am not certain where, but I would expect that a "hg update" appear somewhere in this list of commands executed by continuum..Otherwise all we have is another build the same as the last.
> 2008-11-06 17:38:56,623 [pool-1-thread-1] INFO buildController - Updating working dir
> 2008-11-06 17:38:56,623 [pool-1-thread-1] INFO buildController - Performing action check-working-directory
> 2008-11-06 17:38:56,647 [pool-1-thread-1] INFO buildController - Performing action update-working-directory-from-scm
> 2008-11-06 17:38:56,947 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updating project: Release 1.0 patches', id: '7' to '/u01/app/apache-continuum-1.2.2/target/working-directory/7' with branch/tag release_1_0_patches.
> 2008-11-06 17:38:56,948 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - EXECUTING: /bin/sh -c cd /u01/app/apache-continuum-1.2.2/target/working-directory/7 && hg pull -r release_1_0_patches
> 2008-11-06 17:38:58,560 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - EXECUTING: /bin/sh -c cd /u01/app/apache-continuum-1.2.2/target/working-directory/7 && hg id
> 2008-11-06 17:38:58,959 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - EXECUTING: /bin/sh -c cd /u01/app/apache-continuum-1.2.2/target/working-directory/7 && hg diff -r -1
> 2008-11-06 17:38:59,443 [pool-1-thread-1] INFO buildController - Merging SCM results
> 2008-11-06 17:38:59,492 [pool-1-thread-1] INFO buildController - AlwaysBuild configured, building
> 2008-11-06 17:38:59,493 [pool-1-thread-1] INFO buildController - Performing action update-project-from-working-directory
> 2008-11-06 17:38:59,527 [pool-1-thread-1] INFO action#update-project-from-working-directory - Updating project 'Release 1.0 patches' from checkout.
> 2008-11-06 17:38:59,598 [pool-1-thread-1] INFO buildController - Performing action execute-builder
--
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-1967) the action
action#update-working-directory-from-scm does not update the working
directory when mercurial is the scm being used.
Posted by "Ben Fortuna (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=247263#action_247263 ]
Ben Fortuna commented on CONTINUUM-1967:
----------------------------------------
A workaround that appears to work is to add 'scm:update' to the build definition, ie:
scm:update clean install
> the action action#update-working-directory-from-scm does not update the working directory when mercurial is the scm being used.
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: CONTINUUM-1967
> URL: http://jira.codehaus.org/browse/CONTINUUM-1967
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.2.2
> Environment: Linux, tomcat 5.5.27, continuum 1.2.2.
> Reporter: Rohan Holt
> Fix For: Backlog
>
>
> After some recent changes were made to one of our projects, I performed a continuum build of the project expecting to see the new changes. The changes presented by the "SCM Changes" section of the build results screen confirmed changes existed in the mercurial repository ( local ) however, the required changes did not appear in the deployed application ( deployment is part of the build process ).
> Looking in the logs showed that none of the mercurial commands executed ever updated the working directory with the latest changes.
> I am not certain where, but I would expect that a "hg update" appear somewhere in this list of commands executed by continuum..Otherwise all we have is another build the same as the last.
> 2008-11-06 17:38:56,623 [pool-1-thread-1] INFO buildController - Updating working dir
> 2008-11-06 17:38:56,623 [pool-1-thread-1] INFO buildController - Performing action check-working-directory
> 2008-11-06 17:38:56,647 [pool-1-thread-1] INFO buildController - Performing action update-working-directory-from-scm
> 2008-11-06 17:38:56,947 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updating project: Release 1.0 patches', id: '7' to '/u01/app/apache-continuum-1.2.2/target/working-directory/7' with branch/tag release_1_0_patches.
> 2008-11-06 17:38:56,948 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - EXECUTING: /bin/sh -c cd /u01/app/apache-continuum-1.2.2/target/working-directory/7 && hg pull -r release_1_0_patches
> 2008-11-06 17:38:58,560 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - EXECUTING: /bin/sh -c cd /u01/app/apache-continuum-1.2.2/target/working-directory/7 && hg id
> 2008-11-06 17:38:58,959 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - EXECUTING: /bin/sh -c cd /u01/app/apache-continuum-1.2.2/target/working-directory/7 && hg diff -r -1
> 2008-11-06 17:38:59,443 [pool-1-thread-1] INFO buildController - Merging SCM results
> 2008-11-06 17:38:59,492 [pool-1-thread-1] INFO buildController - AlwaysBuild configured, building
> 2008-11-06 17:38:59,493 [pool-1-thread-1] INFO buildController - Performing action update-project-from-working-directory
> 2008-11-06 17:38:59,527 [pool-1-thread-1] INFO action#update-project-from-working-directory - Updating project 'Release 1.0 patches' from checkout.
> 2008-11-06 17:38:59,598 [pool-1-thread-1] INFO buildController - Performing action execute-builder
--
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