continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuriy Kryshchuk (JIRA)" <>
Subject [jira] Commented: (CONTINUUM-1709) Cannot release within Continuum
Date Wed, 02 Apr 2008 06:15:58 GMT


Yuriy Kryshchuk commented on CONTINUUM-1709:

My environment is configured in following way:

- I added a Maven2 project as http://...../pom.xml using my credentials to access that URL
- the Continuum is running under "builder.snp" account, this account has configured ssh keys
to access the SVN
- it works nice when performing scheduled builds (can update from SVN)

when I make a release from Continuum I have to specify SCM credentials. It is required by
Continuum even if the user running the Apache Tomcat has already access to SVN!
So I enter my username and password to SVN.

And everything works nice until the continuum tries to TAG a version.
I remember my previous attempts (before the builder user) I got in log something like:
svn cannot copy to other repository

So it tried to copy to 

That is correct, but Continuum added to the target URL the username and the entire looked

svn copy from "svn+ssh://svnserver/trunkpath" to "svn+ssh://username@svnserver/tagpath"

And it seems that SVN does not like this and treats them as different repos...

Could you please help me to get it working?

> Cannot release within Continuum
> -------------------------------
>                 Key: CONTINUUM-1709
>                 URL:
>             Project: Continuum
>          Issue Type: Bug
>         Environment: Linux 2.6.18-53.1.6.el5.028stab053.6 #1 SMP Mon Feb 11 20:14:28
MSK 2008 i686 i686 i386 GNU/Linux
>            Reporter: Yuriy Kryshchuk
>            Priority: Critical
>         Attachments: output.txt, release-preparation-input.jpg, release-preparation-result.jpg
> I tried to run the release from the Continuum GUI but I could not.
> The release preparation phase has failed on step "scm-tag".
> When I make a release from my console then it is working.
> More details are attached as screen-shots and logs.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message