Maven SCM

Continuum ignores a new given password for a cvs account until the cvsroot is also changed

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.0
  • Fix Version/s: 1.x
  • Component/s: maven-scm-provider-cvs
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

I changed (only!) the password of a cvs account and set this new password in a project definition in continuum by the web interface. The next build of the project did not work, because of a wrong password (no access to cvs was reported). It seems, that continuum uses the old password although a new password was set. After changing the cvsroot (replaced ip number by dns entry; 100% NOT the reason for this error) the cvs system could be accessed; the new password was used.

Issue Links

is depended upon by

Bug - A problem which impairs or prevents the functions of the product. CONTINUUM-1629 SCM Problem when migrating Continuum to another user account

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Olivier Lamy added a comment -

Not sure it's a scm issue but a continuum one.
Have you tried with last continuum version ?

Show
Olivier Lamy added a comment - Not sure it's a scm issue but a continuum one. Have you tried with last continuum version ?
Hide
Permalink
Fabrício Lemos added a comment -

I could reproduce this bug on Continuum-1.3.4

Show
Fabrício Lemos added a comment - I could reproduce this bug on Continuum-1.3.4
Hide
Permalink
Geert Pante added a comment -

We're having the same issue, also in Continuum.

We're using cvs native provider. When we start a release:prepare from continuum, we always pass in a CVS user name and passwd. But when that passwd is changed, and we pass the new passwd, CVS rejects the login.

We fixed it by removing the cvs user login from .cvspasswd in continuum's home dir.
Changing DNS name by IP number had also the same effect, since this will also result in ignoring the .cvspasswd entry.

I think that CVS will ask for a user login if it's not in .cvspasswd, or the one in .cvspasswd is incorrect. Apparently the native cvs provider only handles the first case.

Greets, Geert.

Show
Geert Pante added a comment - We're having the same issue, also in Continuum. We're using cvs native provider. When we start a release:prepare from continuum, we always pass in a CVS user name and passwd. But when that passwd is changed, and we pass the new passwd, CVS rejects the login. We fixed it by removing the cvs user login from .cvspasswd in continuum's home dir. Changing DNS name by IP number had also the same effect, since this will also result in ignoring the .cvspasswd entry. I think that CVS will ask for a user login if it's not in .cvspasswd, or the one in .cvspasswd is incorrect. Apparently the native cvs provider only handles the first case. Greets, Geert.
Hide
Permalink
Andrei Solntsev added a comment -

We also have this issue not only in Continuum, but in command+line Maven too.
We execute maven-scm-plugin during the build to download common resources from CVS. When user changes CVS password, cvs provider cannot login to cvs.

After debugging the source code, I found that CVS provider stores password in file ~/.cvspasswd, and doesn't refresh it.

Show
Andrei Solntsev added a comment - We also have this issue not only in Continuum, but in command+line Maven too. We execute maven-scm-plugin during the build to download common resources from CVS. When user changes CVS password, cvs provider cannot login to cvs. After debugging the source code, I found that CVS provider stores password in file ~/.cvspasswd, and doesn't refresh it.

People

  • Assignee:
    Unassigned
    Reporter:
    Peter Kehren
Vote (7)
Watch (5)

Dates

  • Created:
    Updated: