You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "deckrider (JIRA)" <ji...@codehaus.org> on 2008/11/17 19:34:41 UTC
[jira] Created: (CONTINUUM-1979) regression from 1.1 to 1.2.2:
projects keep building even without changes
regression from 1.1 to 1.2.2: projects keep building even without changes
-------------------------------------------------------------------------
Key: CONTINUUM-1979
URL: http://jira.codehaus.org/browse/CONTINUUM-1979
Project: Continuum
Issue Type: Bug
Affects Versions: 1.2.2
Reporter: deckrider
We have continuum set up this way on purpose:
POM filename pom.xml
Goals release:prepare release:perform
Arguments --batch-mode
Build Fresh false
Always Build false
Is it default ? true
Schedule DEFAULT_SCHEDULE
Build Environment jdk1.5.0
Description default maven2 buildDefinition
It worked fine with continuum 1.1 stand alone (only projects with real changes would build, but with continuum 1.2.2 stand alone, it builds all projects all the time, even if there are no new changes to subversion.
The log messages are confusing, since at first it leads you to believe the unchanged project won't build, but then it builds anyway:
2008-11-17 18:00:00,033 [continuumScheduler_Worker-6] INFO schedulesActivator - >>>>>>>>>>>>>>>>>>>>> Executing build job (DEFAULT_SCHEDULE)...
2008-11-17 18:00:00,561 [continuumScheduler_Worker-6] INFO continuum - Enqueuing ':: example' with build definition 'Default Maven 2 Build Definition' - id=
3).
2008-11-17 18:00:00,600 [pool-1-thread-1] INFO buildController - Initializing build
2008-11-17 18:00:00,880 [pool-1-thread-1] INFO buildController - Starting build of :: example
2008-11-17 18:00:01,116 [pool-1-thread-1] INFO buildController - Updating working dir
2008-11-17 18:00:01,116 [pool-1-thread-1] INFO buildController - Performing action check-working-directory
2008-11-17 18:00:01,137 [pool-1-thread-1] INFO buildController - Performing action update-working-directory-from-scm
2008-11-17 18:00:01,635 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updating project: :: example', id: '1' to '/opt/app/xyz/var/2-cont
inuum/working-directory/1'.
2008-11-17 18:00:01,976 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - Executing: /bin/sh -c cd /opt/app/xyz/var/2-continuum/work
ing-directory/1 && svn --non-interactive update /opt/app/xyz/var/2-continuum/working-directory/1
2008-11-17 18:00:01,980 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - Working directory: /opt/app/xyz/var/2-continuum/working-di
rectory/1
2008-11-17 18:00:04,399 [pool-1-thread-1] INFO buildController - Merging SCM results
2008-11-17 18:00:05,111 [pool-1-thread-1] INFO buildController - The project was not built because no changes were detected in sources since the last build
.
2008-11-17 18:00:07,305 [pool-1-thread-1] INFO continuumBuildExecutor#maven2 - Found changes in project's version ( maybe project was recently released ),
building
2008-11-17 18:00:07,306 [pool-1-thread-1] INFO buildController - Changes found in the current project, building
2008-11-17 18:00:07,306 [pool-1-thread-1] INFO buildController - Performing action update-project-from-working-directory
2008-11-17 18:00:07,445 [pool-1-thread-1] INFO action#update-project-from-working-directory - Updating project ':: example' from checkout.
2008-11-17 18:00:10,028 [pool-1-thread-1] INFO buildController - Performing action execute-builder
2008-11-17 18:00:11,038 [pool-1-thread-1] WARN continuumBuildExecutor#maven2 - Could not find the executable 'mvn' in this path:
--
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] Assigned: (CONTINUUM-1979) regression from 1.1 to 1.2.2:
projects keep building even without changes
Posted by "Maria Catherine Tan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Catherine Tan reassigned CONTINUUM-1979:
----------------------------------------------
Assignee: Maria Catherine Tan
> regression from 1.1 to 1.2.2: projects keep building even without changes
> -------------------------------------------------------------------------
>
> Key: CONTINUUM-1979
> URL: http://jira.codehaus.org/browse/CONTINUUM-1979
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.2.2
> Reporter: deckrider
> Assignee: Maria Catherine Tan
> Fix For: 1.3.3
>
>
> We have continuum set up this way on purpose:
> POM filename pom.xml
> Goals release:prepare release:perform
> Arguments --batch-mode
> Build Fresh false
> Always Build false
> Is it default ? true
> Schedule DEFAULT_SCHEDULE
> Build Environment jdk1.5.0
> Description default maven2 buildDefinition
> It worked fine with continuum 1.1 stand alone (only projects with real changes would build, but with continuum 1.2.2 stand alone, it builds all projects all the time, even if there are no new changes to subversion.
> The log messages are confusing, since at first it leads you to believe the unchanged project won't build, but then it builds anyway:
> 2008-11-17 18:00:00,033 [continuumScheduler_Worker-6] INFO schedulesActivator - >>>>>>>>>>>>>>>>>>>>> Executing build job (DEFAULT_SCHEDULE)...
> 2008-11-17 18:00:00,561 [continuumScheduler_Worker-6] INFO continuum - Enqueuing ':: example' with build definition 'Default Maven 2 Build Definition' - id=
> 3).
> 2008-11-17 18:00:00,600 [pool-1-thread-1] INFO buildController - Initializing build
> 2008-11-17 18:00:00,880 [pool-1-thread-1] INFO buildController - Starting build of :: example
> 2008-11-17 18:00:01,116 [pool-1-thread-1] INFO buildController - Updating working dir
> 2008-11-17 18:00:01,116 [pool-1-thread-1] INFO buildController - Performing action check-working-directory
> 2008-11-17 18:00:01,137 [pool-1-thread-1] INFO buildController - Performing action update-working-directory-from-scm
> 2008-11-17 18:00:01,635 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updating project: :: example', id: '1' to '/opt/app/xyz/var/2-cont
> inuum/working-directory/1'.
> 2008-11-17 18:00:01,976 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - Executing: /bin/sh -c cd /opt/app/xyz/var/2-continuum/work
> ing-directory/1 && svn --non-interactive update /opt/app/xyz/var/2-continuum/working-directory/1
> 2008-11-17 18:00:01,980 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - Working directory: /opt/app/xyz/var/2-continuum/working-di
> rectory/1
> 2008-11-17 18:00:04,399 [pool-1-thread-1] INFO buildController - Merging SCM results
> 2008-11-17 18:00:05,111 [pool-1-thread-1] INFO buildController - The project was not built because no changes were detected in sources since the last build
> .
> 2008-11-17 18:00:07,305 [pool-1-thread-1] INFO continuumBuildExecutor#maven2 - Found changes in project's version ( maybe project was recently released ),
> building
> 2008-11-17 18:00:07,306 [pool-1-thread-1] INFO buildController - Changes found in the current project, building
> 2008-11-17 18:00:07,306 [pool-1-thread-1] INFO buildController - Performing action update-project-from-working-directory
> 2008-11-17 18:00:07,445 [pool-1-thread-1] INFO action#update-project-from-working-directory - Updating project ':: example' from checkout.
> 2008-11-17 18:00:10,028 [pool-1-thread-1] INFO buildController - Performing action execute-builder
> 2008-11-17 18:00:11,038 [pool-1-thread-1] WARN continuumBuildExecutor#maven2 - Could not find the executable 'mvn' in this path:
--
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-1979) regression from 1.1 to 1.2.2:
projects keep building even without changes
Posted by "deckrider (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=175750#action_175750 ]
deckrider commented on CONTINUUM-1979:
--------------------------------------
Note that I don't use continuum's release functionality. We build a release every time the source code changes by putting 'release:prepare release:deploy' in our default maven2 default build definition goals. So in my case after a release, I think 'scm update' would only pull in changes if someone else had committed changes since the last 'scm update' (which does sometimes happen while the current release is building). But no matter, if there really was a change to continuum's working copy, it should build again. Unless continuum itself made the change (and in that case, there would be no change to continuum's working copy during 'scm update' anyway).
> regression from 1.1 to 1.2.2: projects keep building even without changes
> -------------------------------------------------------------------------
>
> Key: CONTINUUM-1979
> URL: http://jira.codehaus.org/browse/CONTINUUM-1979
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.2.2
> Reporter: deckrider
> Fix For: 1.3.3
>
>
> We have continuum set up this way on purpose:
> POM filename pom.xml
> Goals release:prepare release:perform
> Arguments --batch-mode
> Build Fresh false
> Always Build false
> Is it default ? true
> Schedule DEFAULT_SCHEDULE
> Build Environment jdk1.5.0
> Description default maven2 buildDefinition
> It worked fine with continuum 1.1 stand alone (only projects with real changes would build, but with continuum 1.2.2 stand alone, it builds all projects all the time, even if there are no new changes to subversion.
> The log messages are confusing, since at first it leads you to believe the unchanged project won't build, but then it builds anyway:
> 2008-11-17 18:00:00,033 [continuumScheduler_Worker-6] INFO schedulesActivator - >>>>>>>>>>>>>>>>>>>>> Executing build job (DEFAULT_SCHEDULE)...
> 2008-11-17 18:00:00,561 [continuumScheduler_Worker-6] INFO continuum - Enqueuing ':: example' with build definition 'Default Maven 2 Build Definition' - id=
> 3).
> 2008-11-17 18:00:00,600 [pool-1-thread-1] INFO buildController - Initializing build
> 2008-11-17 18:00:00,880 [pool-1-thread-1] INFO buildController - Starting build of :: example
> 2008-11-17 18:00:01,116 [pool-1-thread-1] INFO buildController - Updating working dir
> 2008-11-17 18:00:01,116 [pool-1-thread-1] INFO buildController - Performing action check-working-directory
> 2008-11-17 18:00:01,137 [pool-1-thread-1] INFO buildController - Performing action update-working-directory-from-scm
> 2008-11-17 18:00:01,635 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updating project: :: example', id: '1' to '/opt/app/xyz/var/2-cont
> inuum/working-directory/1'.
> 2008-11-17 18:00:01,976 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - Executing: /bin/sh -c cd /opt/app/xyz/var/2-continuum/work
> ing-directory/1 && svn --non-interactive update /opt/app/xyz/var/2-continuum/working-directory/1
> 2008-11-17 18:00:01,980 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - Working directory: /opt/app/xyz/var/2-continuum/working-di
> rectory/1
> 2008-11-17 18:00:04,399 [pool-1-thread-1] INFO buildController - Merging SCM results
> 2008-11-17 18:00:05,111 [pool-1-thread-1] INFO buildController - The project was not built because no changes were detected in sources since the last build
> .
> 2008-11-17 18:00:07,305 [pool-1-thread-1] INFO continuumBuildExecutor#maven2 - Found changes in project's version ( maybe project was recently released ),
> building
> 2008-11-17 18:00:07,306 [pool-1-thread-1] INFO buildController - Changes found in the current project, building
> 2008-11-17 18:00:07,306 [pool-1-thread-1] INFO buildController - Performing action update-project-from-working-directory
> 2008-11-17 18:00:07,445 [pool-1-thread-1] INFO action#update-project-from-working-directory - Updating project ':: example' from checkout.
> 2008-11-17 18:00:10,028 [pool-1-thread-1] INFO buildController - Performing action execute-builder
> 2008-11-17 18:00:11,038 [pool-1-thread-1] WARN continuumBuildExecutor#maven2 - Could not find the executable 'mvn' in this path:
--
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] Closed: (CONTINUUM-1979) regression from 1.1 to 1.2.2:
projects keep building even without changes
Posted by "Maria Catherine Tan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Catherine Tan closed CONTINUUM-1979.
------------------------------------------
Resolution: Fixed
revert changes made to CONTINUUM-1815.
fixed in
r777735 of 1.3.x branch
r777737 of trunk
> regression from 1.1 to 1.2.2: projects keep building even without changes
> -------------------------------------------------------------------------
>
> Key: CONTINUUM-1979
> URL: http://jira.codehaus.org/browse/CONTINUUM-1979
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.2.2
> Reporter: deckrider
> Assignee: Maria Catherine Tan
> Fix For: 1.3.3
>
>
> We have continuum set up this way on purpose:
> POM filename pom.xml
> Goals release:prepare release:perform
> Arguments --batch-mode
> Build Fresh false
> Always Build false
> Is it default ? true
> Schedule DEFAULT_SCHEDULE
> Build Environment jdk1.5.0
> Description default maven2 buildDefinition
> It worked fine with continuum 1.1 stand alone (only projects with real changes would build, but with continuum 1.2.2 stand alone, it builds all projects all the time, even if there are no new changes to subversion.
> The log messages are confusing, since at first it leads you to believe the unchanged project won't build, but then it builds anyway:
> 2008-11-17 18:00:00,033 [continuumScheduler_Worker-6] INFO schedulesActivator - >>>>>>>>>>>>>>>>>>>>> Executing build job (DEFAULT_SCHEDULE)...
> 2008-11-17 18:00:00,561 [continuumScheduler_Worker-6] INFO continuum - Enqueuing ':: example' with build definition 'Default Maven 2 Build Definition' - id=
> 3).
> 2008-11-17 18:00:00,600 [pool-1-thread-1] INFO buildController - Initializing build
> 2008-11-17 18:00:00,880 [pool-1-thread-1] INFO buildController - Starting build of :: example
> 2008-11-17 18:00:01,116 [pool-1-thread-1] INFO buildController - Updating working dir
> 2008-11-17 18:00:01,116 [pool-1-thread-1] INFO buildController - Performing action check-working-directory
> 2008-11-17 18:00:01,137 [pool-1-thread-1] INFO buildController - Performing action update-working-directory-from-scm
> 2008-11-17 18:00:01,635 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updating project: :: example', id: '1' to '/opt/app/xyz/var/2-cont
> inuum/working-directory/1'.
> 2008-11-17 18:00:01,976 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - Executing: /bin/sh -c cd /opt/app/xyz/var/2-continuum/work
> ing-directory/1 && svn --non-interactive update /opt/app/xyz/var/2-continuum/working-directory/1
> 2008-11-17 18:00:01,980 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - Working directory: /opt/app/xyz/var/2-continuum/working-di
> rectory/1
> 2008-11-17 18:00:04,399 [pool-1-thread-1] INFO buildController - Merging SCM results
> 2008-11-17 18:00:05,111 [pool-1-thread-1] INFO buildController - The project was not built because no changes were detected in sources since the last build
> .
> 2008-11-17 18:00:07,305 [pool-1-thread-1] INFO continuumBuildExecutor#maven2 - Found changes in project's version ( maybe project was recently released ),
> building
> 2008-11-17 18:00:07,306 [pool-1-thread-1] INFO buildController - Changes found in the current project, building
> 2008-11-17 18:00:07,306 [pool-1-thread-1] INFO buildController - Performing action update-project-from-working-directory
> 2008-11-17 18:00:07,445 [pool-1-thread-1] INFO action#update-project-from-working-directory - Updating project ':: example' from checkout.
> 2008-11-17 18:00:10,028 [pool-1-thread-1] INFO buildController - Performing action execute-builder
> 2008-11-17 18:00:11,038 [pool-1-thread-1] WARN continuumBuildExecutor#maven2 - Could not find the executable 'mvn' in this path:
--
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-1979) regression from 1.1 to 1.2.2:
projects keep building even without changes
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167252#action_167252 ]
Wendy Smoak commented on CONTINUUM-1979:
----------------------------------------
Is this still a problem in 1.2.3 and/or 1.3.1?
> regression from 1.1 to 1.2.2: projects keep building even without changes
> -------------------------------------------------------------------------
>
> Key: CONTINUUM-1979
> URL: http://jira.codehaus.org/browse/CONTINUUM-1979
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.2.2
> Reporter: deckrider
>
> We have continuum set up this way on purpose:
> POM filename pom.xml
> Goals release:prepare release:perform
> Arguments --batch-mode
> Build Fresh false
> Always Build false
> Is it default ? true
> Schedule DEFAULT_SCHEDULE
> Build Environment jdk1.5.0
> Description default maven2 buildDefinition
> It worked fine with continuum 1.1 stand alone (only projects with real changes would build, but with continuum 1.2.2 stand alone, it builds all projects all the time, even if there are no new changes to subversion.
> The log messages are confusing, since at first it leads you to believe the unchanged project won't build, but then it builds anyway:
> 2008-11-17 18:00:00,033 [continuumScheduler_Worker-6] INFO schedulesActivator - >>>>>>>>>>>>>>>>>>>>> Executing build job (DEFAULT_SCHEDULE)...
> 2008-11-17 18:00:00,561 [continuumScheduler_Worker-6] INFO continuum - Enqueuing ':: example' with build definition 'Default Maven 2 Build Definition' - id=
> 3).
> 2008-11-17 18:00:00,600 [pool-1-thread-1] INFO buildController - Initializing build
> 2008-11-17 18:00:00,880 [pool-1-thread-1] INFO buildController - Starting build of :: example
> 2008-11-17 18:00:01,116 [pool-1-thread-1] INFO buildController - Updating working dir
> 2008-11-17 18:00:01,116 [pool-1-thread-1] INFO buildController - Performing action check-working-directory
> 2008-11-17 18:00:01,137 [pool-1-thread-1] INFO buildController - Performing action update-working-directory-from-scm
> 2008-11-17 18:00:01,635 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updating project: :: example', id: '1' to '/opt/app/xyz/var/2-cont
> inuum/working-directory/1'.
> 2008-11-17 18:00:01,976 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - Executing: /bin/sh -c cd /opt/app/xyz/var/2-continuum/work
> ing-directory/1 && svn --non-interactive update /opt/app/xyz/var/2-continuum/working-directory/1
> 2008-11-17 18:00:01,980 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - Working directory: /opt/app/xyz/var/2-continuum/working-di
> rectory/1
> 2008-11-17 18:00:04,399 [pool-1-thread-1] INFO buildController - Merging SCM results
> 2008-11-17 18:00:05,111 [pool-1-thread-1] INFO buildController - The project was not built because no changes were detected in sources since the last build
> .
> 2008-11-17 18:00:07,305 [pool-1-thread-1] INFO continuumBuildExecutor#maven2 - Found changes in project's version ( maybe project was recently released ),
> building
> 2008-11-17 18:00:07,306 [pool-1-thread-1] INFO buildController - Changes found in the current project, building
> 2008-11-17 18:00:07,306 [pool-1-thread-1] INFO buildController - Performing action update-project-from-working-directory
> 2008-11-17 18:00:07,445 [pool-1-thread-1] INFO action#update-project-from-working-directory - Updating project ':: example' from checkout.
> 2008-11-17 18:00:10,028 [pool-1-thread-1] INFO buildController - Performing action execute-builder
> 2008-11-17 18:00:11,038 [pool-1-thread-1] WARN continuumBuildExecutor#maven2 - Could not find the executable 'mvn' in this path:
--
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-1979) regression from 1.1 to 1.2.2:
projects keep building even without changes
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=175691#action_175691 ]
Wendy Smoak commented on CONTINUUM-1979:
----------------------------------------
Perhaps a better solution for CONTINUUM-1815 would be to do an scm update after a release. That would also fix a related problem with trying to release twice in a row.
> regression from 1.1 to 1.2.2: projects keep building even without changes
> -------------------------------------------------------------------------
>
> Key: CONTINUUM-1979
> URL: http://jira.codehaus.org/browse/CONTINUUM-1979
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.2.2
> Reporter: deckrider
> Fix For: 1.3.3
>
>
> We have continuum set up this way on purpose:
> POM filename pom.xml
> Goals release:prepare release:perform
> Arguments --batch-mode
> Build Fresh false
> Always Build false
> Is it default ? true
> Schedule DEFAULT_SCHEDULE
> Build Environment jdk1.5.0
> Description default maven2 buildDefinition
> It worked fine with continuum 1.1 stand alone (only projects with real changes would build, but with continuum 1.2.2 stand alone, it builds all projects all the time, even if there are no new changes to subversion.
> The log messages are confusing, since at first it leads you to believe the unchanged project won't build, but then it builds anyway:
> 2008-11-17 18:00:00,033 [continuumScheduler_Worker-6] INFO schedulesActivator - >>>>>>>>>>>>>>>>>>>>> Executing build job (DEFAULT_SCHEDULE)...
> 2008-11-17 18:00:00,561 [continuumScheduler_Worker-6] INFO continuum - Enqueuing ':: example' with build definition 'Default Maven 2 Build Definition' - id=
> 3).
> 2008-11-17 18:00:00,600 [pool-1-thread-1] INFO buildController - Initializing build
> 2008-11-17 18:00:00,880 [pool-1-thread-1] INFO buildController - Starting build of :: example
> 2008-11-17 18:00:01,116 [pool-1-thread-1] INFO buildController - Updating working dir
> 2008-11-17 18:00:01,116 [pool-1-thread-1] INFO buildController - Performing action check-working-directory
> 2008-11-17 18:00:01,137 [pool-1-thread-1] INFO buildController - Performing action update-working-directory-from-scm
> 2008-11-17 18:00:01,635 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updating project: :: example', id: '1' to '/opt/app/xyz/var/2-cont
> inuum/working-directory/1'.
> 2008-11-17 18:00:01,976 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - Executing: /bin/sh -c cd /opt/app/xyz/var/2-continuum/work
> ing-directory/1 && svn --non-interactive update /opt/app/xyz/var/2-continuum/working-directory/1
> 2008-11-17 18:00:01,980 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - Working directory: /opt/app/xyz/var/2-continuum/working-di
> rectory/1
> 2008-11-17 18:00:04,399 [pool-1-thread-1] INFO buildController - Merging SCM results
> 2008-11-17 18:00:05,111 [pool-1-thread-1] INFO buildController - The project was not built because no changes were detected in sources since the last build
> .
> 2008-11-17 18:00:07,305 [pool-1-thread-1] INFO continuumBuildExecutor#maven2 - Found changes in project's version ( maybe project was recently released ),
> building
> 2008-11-17 18:00:07,306 [pool-1-thread-1] INFO buildController - Changes found in the current project, building
> 2008-11-17 18:00:07,306 [pool-1-thread-1] INFO buildController - Performing action update-project-from-working-directory
> 2008-11-17 18:00:07,445 [pool-1-thread-1] INFO action#update-project-from-working-directory - Updating project ':: example' from checkout.
> 2008-11-17 18:00:10,028 [pool-1-thread-1] INFO buildController - Performing action execute-builder
> 2008-11-17 18:00:11,038 [pool-1-thread-1] WARN continuumBuildExecutor#maven2 - Could not find the executable 'mvn' in this path:
--
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-1979) regression from 1.1 to 1.2.2:
projects keep building even without changes
Posted by "deckrider (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=175677#action_175677 ]
deckrider commented on CONTINUUM-1979:
--------------------------------------
This is still a bug in continuum-1.2.3, and I believe the offending bit addressing CONTINUUM-1815 is from this file:
continuum-core/src/main/java/org/apache/maven/continuum/execution/maven/m2/MavenTwoBuildExecutor.java
{noformat}
//CONTINUUM-1815: additional check for projects recently released
if ( !continuumProject.getVersion().equals( project.getVersion() ) )
{
logger.info( "Found changes in project's version ( maybe project was recently released ), building" );
return true;
}
{noformat}
> regression from 1.1 to 1.2.2: projects keep building even without changes
> -------------------------------------------------------------------------
>
> Key: CONTINUUM-1979
> URL: http://jira.codehaus.org/browse/CONTINUUM-1979
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.2.2
> Reporter: deckrider
> Fix For: 1.3.3
>
>
> We have continuum set up this way on purpose:
> POM filename pom.xml
> Goals release:prepare release:perform
> Arguments --batch-mode
> Build Fresh false
> Always Build false
> Is it default ? true
> Schedule DEFAULT_SCHEDULE
> Build Environment jdk1.5.0
> Description default maven2 buildDefinition
> It worked fine with continuum 1.1 stand alone (only projects with real changes would build, but with continuum 1.2.2 stand alone, it builds all projects all the time, even if there are no new changes to subversion.
> The log messages are confusing, since at first it leads you to believe the unchanged project won't build, but then it builds anyway:
> 2008-11-17 18:00:00,033 [continuumScheduler_Worker-6] INFO schedulesActivator - >>>>>>>>>>>>>>>>>>>>> Executing build job (DEFAULT_SCHEDULE)...
> 2008-11-17 18:00:00,561 [continuumScheduler_Worker-6] INFO continuum - Enqueuing ':: example' with build definition 'Default Maven 2 Build Definition' - id=
> 3).
> 2008-11-17 18:00:00,600 [pool-1-thread-1] INFO buildController - Initializing build
> 2008-11-17 18:00:00,880 [pool-1-thread-1] INFO buildController - Starting build of :: example
> 2008-11-17 18:00:01,116 [pool-1-thread-1] INFO buildController - Updating working dir
> 2008-11-17 18:00:01,116 [pool-1-thread-1] INFO buildController - Performing action check-working-directory
> 2008-11-17 18:00:01,137 [pool-1-thread-1] INFO buildController - Performing action update-working-directory-from-scm
> 2008-11-17 18:00:01,635 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updating project: :: example', id: '1' to '/opt/app/xyz/var/2-cont
> inuum/working-directory/1'.
> 2008-11-17 18:00:01,976 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - Executing: /bin/sh -c cd /opt/app/xyz/var/2-continuum/work
> ing-directory/1 && svn --non-interactive update /opt/app/xyz/var/2-continuum/working-directory/1
> 2008-11-17 18:00:01,980 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - Working directory: /opt/app/xyz/var/2-continuum/working-di
> rectory/1
> 2008-11-17 18:00:04,399 [pool-1-thread-1] INFO buildController - Merging SCM results
> 2008-11-17 18:00:05,111 [pool-1-thread-1] INFO buildController - The project was not built because no changes were detected in sources since the last build
> .
> 2008-11-17 18:00:07,305 [pool-1-thread-1] INFO continuumBuildExecutor#maven2 - Found changes in project's version ( maybe project was recently released ),
> building
> 2008-11-17 18:00:07,306 [pool-1-thread-1] INFO buildController - Changes found in the current project, building
> 2008-11-17 18:00:07,306 [pool-1-thread-1] INFO buildController - Performing action update-project-from-working-directory
> 2008-11-17 18:00:07,445 [pool-1-thread-1] INFO action#update-project-from-working-directory - Updating project ':: example' from checkout.
> 2008-11-17 18:00:10,028 [pool-1-thread-1] INFO buildController - Performing action execute-builder
> 2008-11-17 18:00:11,038 [pool-1-thread-1] WARN continuumBuildExecutor#maven2 - Could not find the executable 'mvn' in this path:
--
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-1979) regression from 1.1 to 1.2.2:
projects keep building even without changes
Posted by "ol (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167990#action_167990 ]
ol commented on CONTINUUM-1979:
-------------------------------
This issue is already present on version 1.2.3.
> regression from 1.1 to 1.2.2: projects keep building even without changes
> -------------------------------------------------------------------------
>
> Key: CONTINUUM-1979
> URL: http://jira.codehaus.org/browse/CONTINUUM-1979
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.2.2
> Reporter: deckrider
>
> We have continuum set up this way on purpose:
> POM filename pom.xml
> Goals release:prepare release:perform
> Arguments --batch-mode
> Build Fresh false
> Always Build false
> Is it default ? true
> Schedule DEFAULT_SCHEDULE
> Build Environment jdk1.5.0
> Description default maven2 buildDefinition
> It worked fine with continuum 1.1 stand alone (only projects with real changes would build, but with continuum 1.2.2 stand alone, it builds all projects all the time, even if there are no new changes to subversion.
> The log messages are confusing, since at first it leads you to believe the unchanged project won't build, but then it builds anyway:
> 2008-11-17 18:00:00,033 [continuumScheduler_Worker-6] INFO schedulesActivator - >>>>>>>>>>>>>>>>>>>>> Executing build job (DEFAULT_SCHEDULE)...
> 2008-11-17 18:00:00,561 [continuumScheduler_Worker-6] INFO continuum - Enqueuing ':: example' with build definition 'Default Maven 2 Build Definition' - id=
> 3).
> 2008-11-17 18:00:00,600 [pool-1-thread-1] INFO buildController - Initializing build
> 2008-11-17 18:00:00,880 [pool-1-thread-1] INFO buildController - Starting build of :: example
> 2008-11-17 18:00:01,116 [pool-1-thread-1] INFO buildController - Updating working dir
> 2008-11-17 18:00:01,116 [pool-1-thread-1] INFO buildController - Performing action check-working-directory
> 2008-11-17 18:00:01,137 [pool-1-thread-1] INFO buildController - Performing action update-working-directory-from-scm
> 2008-11-17 18:00:01,635 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updating project: :: example', id: '1' to '/opt/app/xyz/var/2-cont
> inuum/working-directory/1'.
> 2008-11-17 18:00:01,976 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - Executing: /bin/sh -c cd /opt/app/xyz/var/2-continuum/work
> ing-directory/1 && svn --non-interactive update /opt/app/xyz/var/2-continuum/working-directory/1
> 2008-11-17 18:00:01,980 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - Working directory: /opt/app/xyz/var/2-continuum/working-di
> rectory/1
> 2008-11-17 18:00:04,399 [pool-1-thread-1] INFO buildController - Merging SCM results
> 2008-11-17 18:00:05,111 [pool-1-thread-1] INFO buildController - The project was not built because no changes were detected in sources since the last build
> .
> 2008-11-17 18:00:07,305 [pool-1-thread-1] INFO continuumBuildExecutor#maven2 - Found changes in project's version ( maybe project was recently released ),
> building
> 2008-11-17 18:00:07,306 [pool-1-thread-1] INFO buildController - Changes found in the current project, building
> 2008-11-17 18:00:07,306 [pool-1-thread-1] INFO buildController - Performing action update-project-from-working-directory
> 2008-11-17 18:00:07,445 [pool-1-thread-1] INFO action#update-project-from-working-directory - Updating project ':: example' from checkout.
> 2008-11-17 18:00:10,028 [pool-1-thread-1] INFO buildController - Performing action execute-builder
> 2008-11-17 18:00:11,038 [pool-1-thread-1] WARN continuumBuildExecutor#maven2 - Could not find the executable 'mvn' in this path:
--
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-1979) regression from 1.1 to 1.2.2:
projects keep building even without changes
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated CONTINUUM-1979:
------------------------------------
Fix Version/s: 1.3.3
does sound like a bug - changes in ? files should not trigger a build
> regression from 1.1 to 1.2.2: projects keep building even without changes
> -------------------------------------------------------------------------
>
> Key: CONTINUUM-1979
> URL: http://jira.codehaus.org/browse/CONTINUUM-1979
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.2.2
> Reporter: deckrider
> Fix For: 1.3.3
>
>
> We have continuum set up this way on purpose:
> POM filename pom.xml
> Goals release:prepare release:perform
> Arguments --batch-mode
> Build Fresh false
> Always Build false
> Is it default ? true
> Schedule DEFAULT_SCHEDULE
> Build Environment jdk1.5.0
> Description default maven2 buildDefinition
> It worked fine with continuum 1.1 stand alone (only projects with real changes would build, but with continuum 1.2.2 stand alone, it builds all projects all the time, even if there are no new changes to subversion.
> The log messages are confusing, since at first it leads you to believe the unchanged project won't build, but then it builds anyway:
> 2008-11-17 18:00:00,033 [continuumScheduler_Worker-6] INFO schedulesActivator - >>>>>>>>>>>>>>>>>>>>> Executing build job (DEFAULT_SCHEDULE)...
> 2008-11-17 18:00:00,561 [continuumScheduler_Worker-6] INFO continuum - Enqueuing ':: example' with build definition 'Default Maven 2 Build Definition' - id=
> 3).
> 2008-11-17 18:00:00,600 [pool-1-thread-1] INFO buildController - Initializing build
> 2008-11-17 18:00:00,880 [pool-1-thread-1] INFO buildController - Starting build of :: example
> 2008-11-17 18:00:01,116 [pool-1-thread-1] INFO buildController - Updating working dir
> 2008-11-17 18:00:01,116 [pool-1-thread-1] INFO buildController - Performing action check-working-directory
> 2008-11-17 18:00:01,137 [pool-1-thread-1] INFO buildController - Performing action update-working-directory-from-scm
> 2008-11-17 18:00:01,635 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updating project: :: example', id: '1' to '/opt/app/xyz/var/2-cont
> inuum/working-directory/1'.
> 2008-11-17 18:00:01,976 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - Executing: /bin/sh -c cd /opt/app/xyz/var/2-continuum/work
> ing-directory/1 && svn --non-interactive update /opt/app/xyz/var/2-continuum/working-directory/1
> 2008-11-17 18:00:01,980 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - Working directory: /opt/app/xyz/var/2-continuum/working-di
> rectory/1
> 2008-11-17 18:00:04,399 [pool-1-thread-1] INFO buildController - Merging SCM results
> 2008-11-17 18:00:05,111 [pool-1-thread-1] INFO buildController - The project was not built because no changes were detected in sources since the last build
> .
> 2008-11-17 18:00:07,305 [pool-1-thread-1] INFO continuumBuildExecutor#maven2 - Found changes in project's version ( maybe project was recently released ),
> building
> 2008-11-17 18:00:07,306 [pool-1-thread-1] INFO buildController - Changes found in the current project, building
> 2008-11-17 18:00:07,306 [pool-1-thread-1] INFO buildController - Performing action update-project-from-working-directory
> 2008-11-17 18:00:07,445 [pool-1-thread-1] INFO action#update-project-from-working-directory - Updating project ':: example' from checkout.
> 2008-11-17 18:00:10,028 [pool-1-thread-1] INFO buildController - Performing action execute-builder
> 2008-11-17 18:00:11,038 [pool-1-thread-1] WARN continuumBuildExecutor#maven2 - Could not find the executable 'mvn' in this path:
--
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-1979) regression from 1.1 to 1.2.2:
projects keep building even without changes
Posted by "deckrider (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154734#action_154734 ]
deckrider commented on CONTINUUM-1979:
--------------------------------------
@Maria Catherine Tan:
Yes, as you can see from the above configuration:
Goals release:prepare release:perform
We build a release every time the code changes. Continuum 1.1 realized this and didn't go into a loop building when there were no changes.
> regression from 1.1 to 1.2.2: projects keep building even without changes
> -------------------------------------------------------------------------
>
> Key: CONTINUUM-1979
> URL: http://jira.codehaus.org/browse/CONTINUUM-1979
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.2.2
> Reporter: deckrider
>
> We have continuum set up this way on purpose:
> POM filename pom.xml
> Goals release:prepare release:perform
> Arguments --batch-mode
> Build Fresh false
> Always Build false
> Is it default ? true
> Schedule DEFAULT_SCHEDULE
> Build Environment jdk1.5.0
> Description default maven2 buildDefinition
> It worked fine with continuum 1.1 stand alone (only projects with real changes would build, but with continuum 1.2.2 stand alone, it builds all projects all the time, even if there are no new changes to subversion.
> The log messages are confusing, since at first it leads you to believe the unchanged project won't build, but then it builds anyway:
> 2008-11-17 18:00:00,033 [continuumScheduler_Worker-6] INFO schedulesActivator - >>>>>>>>>>>>>>>>>>>>> Executing build job (DEFAULT_SCHEDULE)...
> 2008-11-17 18:00:00,561 [continuumScheduler_Worker-6] INFO continuum - Enqueuing ':: example' with build definition 'Default Maven 2 Build Definition' - id=
> 3).
> 2008-11-17 18:00:00,600 [pool-1-thread-1] INFO buildController - Initializing build
> 2008-11-17 18:00:00,880 [pool-1-thread-1] INFO buildController - Starting build of :: example
> 2008-11-17 18:00:01,116 [pool-1-thread-1] INFO buildController - Updating working dir
> 2008-11-17 18:00:01,116 [pool-1-thread-1] INFO buildController - Performing action check-working-directory
> 2008-11-17 18:00:01,137 [pool-1-thread-1] INFO buildController - Performing action update-working-directory-from-scm
> 2008-11-17 18:00:01,635 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updating project: :: example', id: '1' to '/opt/app/xyz/var/2-cont
> inuum/working-directory/1'.
> 2008-11-17 18:00:01,976 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - Executing: /bin/sh -c cd /opt/app/xyz/var/2-continuum/work
> ing-directory/1 && svn --non-interactive update /opt/app/xyz/var/2-continuum/working-directory/1
> 2008-11-17 18:00:01,980 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - Working directory: /opt/app/xyz/var/2-continuum/working-di
> rectory/1
> 2008-11-17 18:00:04,399 [pool-1-thread-1] INFO buildController - Merging SCM results
> 2008-11-17 18:00:05,111 [pool-1-thread-1] INFO buildController - The project was not built because no changes were detected in sources since the last build
> .
> 2008-11-17 18:00:07,305 [pool-1-thread-1] INFO continuumBuildExecutor#maven2 - Found changes in project's version ( maybe project was recently released ),
> building
> 2008-11-17 18:00:07,306 [pool-1-thread-1] INFO buildController - Changes found in the current project, building
> 2008-11-17 18:00:07,306 [pool-1-thread-1] INFO buildController - Performing action update-project-from-working-directory
> 2008-11-17 18:00:07,445 [pool-1-thread-1] INFO action#update-project-from-working-directory - Updating project ':: example' from checkout.
> 2008-11-17 18:00:10,028 [pool-1-thread-1] INFO buildController - Performing action execute-builder
> 2008-11-17 18:00:11,038 [pool-1-thread-1] WARN continuumBuildExecutor#maven2 - Could not find the executable 'mvn' in this path:
--
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-1979) regression from 1.1 to 1.2.2:
projects keep building even without changes
Posted by "deckrider (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=175684#action_175684 ]
deckrider commented on CONTINUUM-1979:
--------------------------------------
I've built continuum 1.2.3 commenting out the above code and it addresses this issue.
I've compared 1.2.3 source with 1.3.2 source of this file:
continuum-core/src/main/java/org/apache/maven/continuum/execution/maven/m2/MavenTwoBuildExecutor.java
Since the above block of code is still there and since this file has hardly changed (except for logging changes), I assume 1.3.2 still has the issue.
> regression from 1.1 to 1.2.2: projects keep building even without changes
> -------------------------------------------------------------------------
>
> Key: CONTINUUM-1979
> URL: http://jira.codehaus.org/browse/CONTINUUM-1979
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.2.2
> Reporter: deckrider
> Fix For: 1.3.3
>
>
> We have continuum set up this way on purpose:
> POM filename pom.xml
> Goals release:prepare release:perform
> Arguments --batch-mode
> Build Fresh false
> Always Build false
> Is it default ? true
> Schedule DEFAULT_SCHEDULE
> Build Environment jdk1.5.0
> Description default maven2 buildDefinition
> It worked fine with continuum 1.1 stand alone (only projects with real changes would build, but with continuum 1.2.2 stand alone, it builds all projects all the time, even if there are no new changes to subversion.
> The log messages are confusing, since at first it leads you to believe the unchanged project won't build, but then it builds anyway:
> 2008-11-17 18:00:00,033 [continuumScheduler_Worker-6] INFO schedulesActivator - >>>>>>>>>>>>>>>>>>>>> Executing build job (DEFAULT_SCHEDULE)...
> 2008-11-17 18:00:00,561 [continuumScheduler_Worker-6] INFO continuum - Enqueuing ':: example' with build definition 'Default Maven 2 Build Definition' - id=
> 3).
> 2008-11-17 18:00:00,600 [pool-1-thread-1] INFO buildController - Initializing build
> 2008-11-17 18:00:00,880 [pool-1-thread-1] INFO buildController - Starting build of :: example
> 2008-11-17 18:00:01,116 [pool-1-thread-1] INFO buildController - Updating working dir
> 2008-11-17 18:00:01,116 [pool-1-thread-1] INFO buildController - Performing action check-working-directory
> 2008-11-17 18:00:01,137 [pool-1-thread-1] INFO buildController - Performing action update-working-directory-from-scm
> 2008-11-17 18:00:01,635 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updating project: :: example', id: '1' to '/opt/app/xyz/var/2-cont
> inuum/working-directory/1'.
> 2008-11-17 18:00:01,976 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - Executing: /bin/sh -c cd /opt/app/xyz/var/2-continuum/work
> ing-directory/1 && svn --non-interactive update /opt/app/xyz/var/2-continuum/working-directory/1
> 2008-11-17 18:00:01,980 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - Working directory: /opt/app/xyz/var/2-continuum/working-di
> rectory/1
> 2008-11-17 18:00:04,399 [pool-1-thread-1] INFO buildController - Merging SCM results
> 2008-11-17 18:00:05,111 [pool-1-thread-1] INFO buildController - The project was not built because no changes were detected in sources since the last build
> .
> 2008-11-17 18:00:07,305 [pool-1-thread-1] INFO continuumBuildExecutor#maven2 - Found changes in project's version ( maybe project was recently released ),
> building
> 2008-11-17 18:00:07,306 [pool-1-thread-1] INFO buildController - Changes found in the current project, building
> 2008-11-17 18:00:07,306 [pool-1-thread-1] INFO buildController - Performing action update-project-from-working-directory
> 2008-11-17 18:00:07,445 [pool-1-thread-1] INFO action#update-project-from-working-directory - Updating project ':: example' from checkout.
> 2008-11-17 18:00:10,028 [pool-1-thread-1] INFO buildController - Performing action execute-builder
> 2008-11-17 18:00:11,038 [pool-1-thread-1] WARN continuumBuildExecutor#maven2 - Could not find the executable 'mvn' in this path:
--
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-1979) regression from 1.1 to 1.2.2:
projects keep building even without changes
Posted by "Maria Catherine Tan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154679#action_154679 ]
Maria Catherine Tan commented on CONTINUUM-1979:
------------------------------------------------
Did you recently released this particular project?
It seems like it did based on the log.
2008-11-17 18:00:07,305 [pool-1-thread-1] INFO continuumBuildExecutor#maven2 - Found changes in project's version ( maybe project was recently released ),
building
If a scheduled build was triggered for the first time after a release, continuum will still build the project to update the project's version even if no changes were detected in sources.
> regression from 1.1 to 1.2.2: projects keep building even without changes
> -------------------------------------------------------------------------
>
> Key: CONTINUUM-1979
> URL: http://jira.codehaus.org/browse/CONTINUUM-1979
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.2.2
> Reporter: deckrider
>
> We have continuum set up this way on purpose:
> POM filename pom.xml
> Goals release:prepare release:perform
> Arguments --batch-mode
> Build Fresh false
> Always Build false
> Is it default ? true
> Schedule DEFAULT_SCHEDULE
> Build Environment jdk1.5.0
> Description default maven2 buildDefinition
> It worked fine with continuum 1.1 stand alone (only projects with real changes would build, but with continuum 1.2.2 stand alone, it builds all projects all the time, even if there are no new changes to subversion.
> The log messages are confusing, since at first it leads you to believe the unchanged project won't build, but then it builds anyway:
> 2008-11-17 18:00:00,033 [continuumScheduler_Worker-6] INFO schedulesActivator - >>>>>>>>>>>>>>>>>>>>> Executing build job (DEFAULT_SCHEDULE)...
> 2008-11-17 18:00:00,561 [continuumScheduler_Worker-6] INFO continuum - Enqueuing ':: example' with build definition 'Default Maven 2 Build Definition' - id=
> 3).
> 2008-11-17 18:00:00,600 [pool-1-thread-1] INFO buildController - Initializing build
> 2008-11-17 18:00:00,880 [pool-1-thread-1] INFO buildController - Starting build of :: example
> 2008-11-17 18:00:01,116 [pool-1-thread-1] INFO buildController - Updating working dir
> 2008-11-17 18:00:01,116 [pool-1-thread-1] INFO buildController - Performing action check-working-directory
> 2008-11-17 18:00:01,137 [pool-1-thread-1] INFO buildController - Performing action update-working-directory-from-scm
> 2008-11-17 18:00:01,635 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updating project: :: example', id: '1' to '/opt/app/xyz/var/2-cont
> inuum/working-directory/1'.
> 2008-11-17 18:00:01,976 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - Executing: /bin/sh -c cd /opt/app/xyz/var/2-continuum/work
> ing-directory/1 && svn --non-interactive update /opt/app/xyz/var/2-continuum/working-directory/1
> 2008-11-17 18:00:01,980 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - Working directory: /opt/app/xyz/var/2-continuum/working-di
> rectory/1
> 2008-11-17 18:00:04,399 [pool-1-thread-1] INFO buildController - Merging SCM results
> 2008-11-17 18:00:05,111 [pool-1-thread-1] INFO buildController - The project was not built because no changes were detected in sources since the last build
> .
> 2008-11-17 18:00:07,305 [pool-1-thread-1] INFO continuumBuildExecutor#maven2 - Found changes in project's version ( maybe project was recently released ),
> building
> 2008-11-17 18:00:07,306 [pool-1-thread-1] INFO buildController - Changes found in the current project, building
> 2008-11-17 18:00:07,306 [pool-1-thread-1] INFO buildController - Performing action update-project-from-working-directory
> 2008-11-17 18:00:07,445 [pool-1-thread-1] INFO action#update-project-from-working-directory - Updating project ':: example' from checkout.
> 2008-11-17 18:00:10,028 [pool-1-thread-1] INFO buildController - Performing action execute-builder
> 2008-11-17 18:00:11,038 [pool-1-thread-1] WARN continuumBuildExecutor#maven2 - Could not find the executable 'mvn' in this path:
--
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-1979) regression from 1.1 to 1.2.2:
projects keep building even without changes
Posted by "ol (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168003#action_168003 ]
ol commented on CONTINUUM-1979:
-------------------------------
We found the problem.
It concerns the 'target' folder.
This folder is not specified in the .cvsignore file => continuum thinks there is a difference => continuum launches the build.
Here is the log line : 2009-03-05 14:24:36,564 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updated 1 files.
For a project with a .cvsignore containing the 'target' folder, the build is not launched.
But why is this behavior different from continuum 1.1 ???
> regression from 1.1 to 1.2.2: projects keep building even without changes
> -------------------------------------------------------------------------
>
> Key: CONTINUUM-1979
> URL: http://jira.codehaus.org/browse/CONTINUUM-1979
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.2.2
> Reporter: deckrider
>
> We have continuum set up this way on purpose:
> POM filename pom.xml
> Goals release:prepare release:perform
> Arguments --batch-mode
> Build Fresh false
> Always Build false
> Is it default ? true
> Schedule DEFAULT_SCHEDULE
> Build Environment jdk1.5.0
> Description default maven2 buildDefinition
> It worked fine with continuum 1.1 stand alone (only projects with real changes would build, but with continuum 1.2.2 stand alone, it builds all projects all the time, even if there are no new changes to subversion.
> The log messages are confusing, since at first it leads you to believe the unchanged project won't build, but then it builds anyway:
> 2008-11-17 18:00:00,033 [continuumScheduler_Worker-6] INFO schedulesActivator - >>>>>>>>>>>>>>>>>>>>> Executing build job (DEFAULT_SCHEDULE)...
> 2008-11-17 18:00:00,561 [continuumScheduler_Worker-6] INFO continuum - Enqueuing ':: example' with build definition 'Default Maven 2 Build Definition' - id=
> 3).
> 2008-11-17 18:00:00,600 [pool-1-thread-1] INFO buildController - Initializing build
> 2008-11-17 18:00:00,880 [pool-1-thread-1] INFO buildController - Starting build of :: example
> 2008-11-17 18:00:01,116 [pool-1-thread-1] INFO buildController - Updating working dir
> 2008-11-17 18:00:01,116 [pool-1-thread-1] INFO buildController - Performing action check-working-directory
> 2008-11-17 18:00:01,137 [pool-1-thread-1] INFO buildController - Performing action update-working-directory-from-scm
> 2008-11-17 18:00:01,635 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updating project: :: example', id: '1' to '/opt/app/xyz/var/2-cont
> inuum/working-directory/1'.
> 2008-11-17 18:00:01,976 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - Executing: /bin/sh -c cd /opt/app/xyz/var/2-continuum/work
> ing-directory/1 && svn --non-interactive update /opt/app/xyz/var/2-continuum/working-directory/1
> 2008-11-17 18:00:01,980 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - Working directory: /opt/app/xyz/var/2-continuum/working-di
> rectory/1
> 2008-11-17 18:00:04,399 [pool-1-thread-1] INFO buildController - Merging SCM results
> 2008-11-17 18:00:05,111 [pool-1-thread-1] INFO buildController - The project was not built because no changes were detected in sources since the last build
> .
> 2008-11-17 18:00:07,305 [pool-1-thread-1] INFO continuumBuildExecutor#maven2 - Found changes in project's version ( maybe project was recently released ),
> building
> 2008-11-17 18:00:07,306 [pool-1-thread-1] INFO buildController - Changes found in the current project, building
> 2008-11-17 18:00:07,306 [pool-1-thread-1] INFO buildController - Performing action update-project-from-working-directory
> 2008-11-17 18:00:07,445 [pool-1-thread-1] INFO action#update-project-from-working-directory - Updating project ':: example' from checkout.
> 2008-11-17 18:00:10,028 [pool-1-thread-1] INFO buildController - Performing action execute-builder
> 2008-11-17 18:00:11,038 [pool-1-thread-1] WARN continuumBuildExecutor#maven2 - Could not find the executable 'mvn' in this path:
--
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