[
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
