You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@continuum.apache.org by Janne Rantala <ja...@gmail.com> on 2009/02/20 22:37:34 UTC
Continuum builds even without scm changes
Hi,
I have Maven 2 project with no subprojects. The problem is that Maven builds
with goals set to clean install even if there are no scm changes. When I
check build, it shows folder target in scm changes. I've tried adding target
folder to .cvsignore -file but that had no effect. What's the proper way to
build only when there is changes in cvs repository?
Best regards,
Janne
Re: Continuum builds even without scm changes
Posted by Janne Rantala <ja...@gmail.com>.
2009/2/21 Wendy Smoak <ws...@gmail.com>
> On Sat, Feb 21, 2009 at 1:27 AM, Janne Rantala <ja...@gmail.com>
> wrote:
>
> > Target directory is not under version control, only src directory and
> > pom.xml are. However, my tests generate some of the files under target,
> > could this be triggering the build?
>
> It shouldn't be. What version of Continuum are you using? What does
> the log file say when it builds the project?
>
> Earlier, you wrote, "When I check build, it shows folder target in scm
> changes."
> What are you checking? Something in Continuum, or just visually on
> the file system?
>
> Also make sure that 'Build Fresh' and 'Always Build' are _not_ checked
> in this build definition.
>
> --
> Wendy
>
I'm using Continuum 1.2.2. By checking the build I meant checking build
result from Continuum. Both 'Build fresh' and 'Always build' fields are not
checked.
Here's the log file from continuum.log:
2009-02-21 21:00:33,621 [pool-1-thread-1] INFO buildController -
Initializing build
2009-02-21 21:00:33,669 [pool-1-thread-1] INFO buildController - Starting
build of testproject
2009-02-21 21:00:33,700 [pool-1-thread-1] INFO buildController - Updating
working dir
2009-02-21 21:00:33,701 [pool-1-thread-1] INFO buildController -
Performing action check-working-directory
2009-02-21 21:00:33,704 [pool-1-thread-1] INFO buildController -
Performing action update-working-directory-from-scm
2009-02-21 21:00:33,765 [pool-1-thread-1] INFO
action#update-working-directory-from-scm - Updating project: testproject',
id: '21' to '/ext/continuum/work/21'.
2009-02-21 21:00:33,767 [pool-1-thread-1] INFO
org.apache.continuum.scm.manager.Slf4jScmLogger - Executing: /bin/sh -c cd
/ext/continuum/work/21 && cvs -z3 -f -q update -d
2009-02-21 21:00:33,767 [pool-1-thread-1] INFO
org.apache.continuum.scm.manager.Slf4jScmLogger - Working directory:
/ext/continuum/work/21
2009-02-21 21:00:36,807 [pool-1-thread-1] INFO
org.apache.continuum.scm.manager.Slf4jScmLogger - Executing: /bin/sh -c cd
/ext/continuum/work/21 && cvs -z3 -f -d
:pserver:snetcvsuser@cvsserver:/cvsroot/internal/industry/snet-net
-q log -d '2009-02-20 21:01:01+0200<2009-02-21 21:00:36+0200'
2009-02-21 21:00:36,807 [pool-1-thread-1] INFO
org.apache.continuum.scm.manager.Slf4jScmLogger - Working directory:
/ext/continuum/work/21
2009-02-21 21:00:38,531 [pool-1-thread-1] INFO
action#update-working-directory-from-scm - Updated 1 files.
2009-02-21 21:00:38,575 [pool-1-thread-1] INFO buildController - Merging
SCM results
2009-02-21 21:00:38,630 [pool-1-thread-1] INFO buildController - The
project was not built because all changes are unknown (maybe local
modifications or ignored files not defined in your SCM tool.
2009-02-21 21:00:38,672 [pool-1-thread-1] INFO buildController - Changes
found in the current project, building
2009-02-21 21:00:38,672 [pool-1-thread-1] INFO buildController -
Performing action update-project-from-working-directory
2009-02-21 21:00:38,683 [pool-1-thread-1] INFO
action#update-project-from-working-directory - Updating project
'testproject' from checkout.
2009-02-21 21:00:38,912 [pool-1-thread-1] INFO buildController -
Performing action execute-builder
2009-02-21 21:00:39,032 [pool-1-thread-1] WARN
continuumBuildExecutor#maven2 - Could not find the executable 'mvn' in this
path:
2009-02-21 21:00:39,118 [pool-1-thread-1] INFO shellCommandHelper -
Executing: /bin/sh -c cd /ext/continuum/work/21 && mvn --batch-mode
--non-recursive -Dcontinuum.project.lastBuild.state=2
-Dcontinuum.project.nextBuild.number=27 -Dcontinuum.project.name=testproject
-Dcontinuum.project.id=21 -Dcontinuum.project.version=1.0.0-SNAPSHOT -
Dcontinuum.project.group.name=testproject
-Dcontinuum.project.lastBuild.number=26
-Dmaven.repo.local=/ext/maven/repository clean install
2009-02-21 21:00:39,119 [pool-1-thread-1] INFO shellCommandHelper -
Working directory: /ext/continuum/work/21
2009-02-21 21:03:37,286 [pool-1-thread-1] INFO
continuumBuildExecutor#maven2 - Exit code: 0
2009-02-21 21:03:37,472 [pool-1-thread-1] INFO
continuumBuildExecutor#maven2 - Backup surefire files.
2009-02-21 21:03:37,475 [pool-1-thread-1] INFO buildController -
Performing action deploy-artifact
2009-02-21 21:03:37,588 [pool-1-thread-1] INFO
org.apache.maven.continuum.notification.mail.MailContinuumNotifier - Same
state, not sending message.
2009-02-21 21:03:37,589 [pool-1-thread-1] INFO
org.apache.maven.continuum.notification.mail.MailContinuumNotifier - Same
state, not sending message.
2009-02-21 21:03:40,322 [pool-1-thread-1] ERROR velocityComponent - RHS of
#set statement is null. Context will not be modified.
org/apache/maven/continuum/notification/mail/templates/maven2/BuildComplete.vm
[line 43, column 1]
2009-02-21 21:03:40,328 [pool-1-thread-1] INFO
org.apache.maven.continuum.notification.mail.MailContinuumNotifier - No
mail notifier for 'testproject'.
stderrout.log shows some strange errors, could this be the reason?
org.netbeans.lib.cvsclient.connection.AuthenticationException:
Authentication failed. Response from server was: "E PAM authe".
at
org.netbeans.lib.cvsclient.connection.PServerConnection.openConnection(PServerConnection.java:238)
at
org.netbeans.lib.cvsclient.connection.PServerConnection.open(PServerConnection.java:326)
at
org.apache.maven.scm.provider.cvslib.cvsjava.util.CvsConnection.connect(CvsConnection.java:166)
at
org.apache.maven.scm.provider.cvslib.cvsjava.util.CvsConnection.processCommand(CvsConnection.java:477)
at
org.apache.maven.scm.provider.cvslib.cvsjava.command.changelog.CvsJavaChangeLogCommand.executeCvsCommand(CvsJavaChangeLogCommand.java:55)
at
org.apache.maven.scm.provider.cvslib.command.changelog.AbstractCvsChangeLogCommand.executeChangeLogCommand(AbstractCvsChangeLogCommand.java:111)
at
org.apache.maven.scm.provider.cvslib.command.changelog.AbstractCvsChangeLogCommand.executeChangeLogCommand(AbstractCvsChangeLogCommand.java:63)
at
org.apache.maven.scm.command.changelog.AbstractChangeLogCommand.executeCommand(AbstractChangeLogCommand.java:103)
at
org.apache.maven.scm.command.update.AbstractUpdateCommand.executeCommand(AbstractUpdateCommand.java:76)
at
org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59)
at
org.apache.maven.scm.provider.cvslib.AbstractCvsScmProvider.executeCommand(AbstractCvsScmProvider.java:548)
at
org.apache.maven.scm.provider.cvslib.AbstractCvsScmProvider.update(AbstractCvsScmProvider.java:662)
at
org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:851)
at
org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:812)
at
org.apache.maven.scm.manager.AbstractScmManager.update(AbstractScmManager.java:555)
at
org.apache.continuum.scm.DefaultContinuumScm.update(DefaultContinuumScm.java:129)
at
org.apache.maven.continuum.core.action.UpdateWorkingDirectoryFromScmContinuumAction.execute(UpdateWorkingDirectoryFromScmContinuumAction.java:120)
at
org.apache.maven.continuum.buildcontroller.DefaultBuildController.performAction(DefaultBuildController.java:435)
at
org.apache.maven.continuum.buildcontroller.DefaultBuildController.updateWorkingDirectory(DefaultBuildController.java:407)
at
org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:133)
at
org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:50)
at
org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116)
at
edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
at
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:178)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
at java.lang.Thread.run(Thread.java:595)
Best regards,
Janne
Re: Continuum builds even without scm changes
Posted by Wendy Smoak <ws...@gmail.com>.
On Sat, Feb 21, 2009 at 1:27 AM, Janne Rantala <ja...@gmail.com> wrote:
> Target directory is not under version control, only src directory and
> pom.xml are. However, my tests generate some of the files under target,
> could this be triggering the build?
It shouldn't be. What version of Continuum are you using? What does
the log file say when it builds the project?
Earlier, you wrote, "When I check build, it shows folder target in scm
changes."
What are you checking? Something in Continuum, or just visually on
the file system?
Also make sure that 'Build Fresh' and 'Always Build' are _not_ checked
in this build definition.
--
Wendy
Re: Continuum builds even without scm changes
Posted by Janne Rantala <ja...@gmail.com>.
2009/2/21 Wendy Smoak <ws...@gmail.com>
> On Fri, Feb 20, 2009 at 2:37 PM, Janne Rantala <ja...@gmail.com>
> wrote:
>
> > I have Maven 2 project with no subprojects. The problem is that Maven
> builds
> > with goals set to clean install even if there are no scm changes. When I
> > check build, it shows folder target in scm changes. I've tried adding
> target
> > folder to .cvsignore -file but that had no effect. What's the proper way
> to
> > build only when there is changes in cvs repository?
>
> It sounds like your target directory is under version control. If so,
> I'm not sure adding it to the ignores will help, you probably need to
> remove it from version control by deleting it and committing the
> change.
>
> (I'm not familiar with CVS, this is what I would do if it happened to
> a project in Subversion.)
>
> --
> Wendy
>
Hi,
Target directory is not under version control, only src directory and
pom.xml are. However, my tests generate some of the files under target,
could this be triggering the build?
Best Regards,
Janne
Re: Continuum builds even without scm changes
Posted by Wendy Smoak <ws...@gmail.com>.
On Fri, Feb 20, 2009 at 2:37 PM, Janne Rantala <ja...@gmail.com> wrote:
> I have Maven 2 project with no subprojects. The problem is that Maven builds
> with goals set to clean install even if there are no scm changes. When I
> check build, it shows folder target in scm changes. I've tried adding target
> folder to .cvsignore -file but that had no effect. What's the proper way to
> build only when there is changes in cvs repository?
It sounds like your target directory is under version control. If so,
I'm not sure adding it to the ignores will help, you probably need to
remove it from version control by deleting it and committing the
change.
(I'm not familiar with CVS, this is what I would do if it happened to
a project in Subversion.)
--
Wendy