Continuum

Releasing secured projects will not prompt username/password needed with SCM Username and SCM Password not provided on release:perform goals

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.3.3 (Beta)
  • Fix Version/s: Backlog
  • Component/s: None
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

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.

Issue Links

This issue is related to:
CONTINUUM-2272 Able to add secured projects without credentials Major Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Wendy Smoak added a comment -

Is this with Subversion? Did you check the 'use cached credentials if available' checkbox when you added the project in step 1?

My guess is it's probably using cached credentials.

I don't think it needs to prompt – there are already fields on the 'prepare release' form that the user should fill in.

Not sure this is a bug, it's just how Subversion works if you don't explicitly tell it not to cache credentials.

Show
Wendy Smoak added a comment - Is this with Subversion? Did you check the 'use cached credentials if available' checkbox when you added the project in step 1? My guess is it's probably using cached credentials. I don't think it needs to prompt – there are already fields on the 'prepare release' form that the user should fill in. Not sure this is a bug, it's just how Subversion works if you don't explicitly tell it not to cache credentials.
Hide
Permalink
Maria Catherine Tan added a comment -

I tried adding a project without checking the 'use cached credentials' and then release it without providing credentials and I got a successful release prepare.

Is this a bug?

Show
Maria Catherine Tan added a comment - I tried adding a project without checking the 'use cached credentials' and then release it without providing credentials and I got a successful release prepare. Is this a bug?
Hide
Permalink
Wendy Smoak added a comment -

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.

Show
Wendy Smoak added a comment - 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.
Hide
Permalink
Wendy Smoak added a comment -

Looks like CONTINUUM-2272 may have just changed the behavior I was describing.

Show
Wendy Smoak added a comment - Looks like CONTINUUM-2272 may have just changed the behavior I was describing.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.