[
http://jira.codehaus.org/browse/CONTINUUM-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180816#action_180816
]
Wendy Smoak commented on CONTINUUM-2251:
----------------------------------------
I don't think it's a bug.
1. If you provide credentials on the release form, Continuum will pass them
through (to Subversion, I assume, as --username and --password.) Then either
a. the credentials will work and release prepare will succeed
b. the credentials are bad and it will fail
2. If you don't provide credentials on the release form, Continuum won't pass
them through on the command line. In that case, Subversion will either
a. use credentials that are already cached for the user in question
b. fail because no credentials were passed and there are none cached
My guess is that you're doing this on your development box and you've checked
out this project (or another from the same realm) at some point in the past, so
you're in scenario 2a.
I don't think the 'use cached credentials' checkbox in Continuum directly
applies to the release process. Maybe that label should be changed to '... for
checkout and update'.
Let's leave this open until we figure out exactly what's happening and update
the docs so it's clear.
> Releasing secured projects will not prompt username/password needed with SCM
> Username and SCM Password not provided on release:perform goals
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CONTINUUM-2251
> URL: http://jira.codehaus.org/browse/CONTINUUM-2251
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.3.3
> Reporter: Marecor Baclay
>
> Steps to replicate:
> 1. Add a secured project
> 2. Build the project
> 3. Release the project
> - in release:prepare, do not provide values in SCM Username and SCM Password
> actual result:
> release:perform goal was successful.
> It should not execute the release:perform goal, thus it must prompt a message
> asking for the SCM Username and SCM Password.
--
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
