continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wendy Smoak (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (CONTINUUM-2043) Release should happen on a build agent rather than on the master
Date Mon, 16 Mar 2009 15:50:12 GMT

    [ http://jira.codehaus.org/browse/CONTINUUM-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169822#action_169822
] 

Wendy Smoak commented on CONTINUUM-2043:
----------------------------------------

Thanks for the explanation.  Yes it makes sense that you have to have a successful build prior
to a release (though the UI could do a better job at telling you what's going on.  Right now
it just refuses to do the release and doesn't give you any message.)

When I tested releasing on a build agent, It failed at the scm-commit-release phase with the
following output:
[ERROR] org.apache.maven.shared.release.scm.ReleaseScmCommandException: Unable to commit files
Provider message:
The svn command failed.
Command output:
svn: '/Users/wsmoak/svn/continuum/continuum/continuum-buildagent/continuum-buildagent-webapp/working-directory/6/working-directory/6'
is not a working copy
svn: Can't open file '/Users/wsmoak/svn/continuum/continuum/continuum-buildagent/continuum-buildagent-webapp/working-directory/6/working-directory/6/.svn/entries':
No such file or directory

	at org.apache.maven.shared.release.phase.ScmCommitPhase.checkin(ScmCommitPhase.java:133)
	at org.apache.maven.shared.release.phase.ScmCommitPhase.execute(ScmCommitPhase.java:109)
	at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:194)
	at org.apache.maven.shared.release.DefaultReleaseManager.prepareWithResult(DefaultReleaseManager.java:107)
	at org.apache.maven.continuum.release.executors.PrepareReleaseTaskExecutor.execute(PrepareReleaseTaskExecutor.java:44)
	at org.apache.maven.continuum.release.executors.AbstractReleaseTaskExecutor.executeTask(AbstractReleaseTaskExecutor.java:68)
	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:176)
	at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
	at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
	at java.lang.Thread.run(Thread.java:637)

Note that 'working-directory/6' is duplicated in the path it's trying to use.

My configuration on the build agent is simply 
     <buildOutputDirectory>build-output-directory</buildOutputDirectory>
(not a full path).


> Release should happen on a build agent rather than on the master
> ----------------------------------------------------------------
>
>                 Key: CONTINUUM-2043
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-2043
>             Project: Continuum
>          Issue Type: Improvement
>          Components: Distributed Builds
>    Affects Versions: 1.3.1
>            Reporter: Wendy Smoak
>            Assignee: Maria Catherine Tan
>             Fix For: 1.3.2
>
>
> When the distributed builds feature is enabled, releases should happen on a build agent
instead of the master.
> Will need to reverse the change made for CONTINUUM-2035 which checks out code on the
master.
> Related to CONTINUUM-2042, Ability to control which build agent a project builds on.

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

        

Mime
View raw message