Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-59096

Mercurial plugin stops working after password change

XMLWordPrintable

      I have a pipeline-job with mercurial SCM working for some time now.

      Currently the password policy forced me to change the password. Since that time the job stopped working with the following output:

      Started by user xxx
      Checking out hg http://myserver/hg/product/ default into D:\workdir\build\mybuild\workspace@script to read Jenkins/Jenkinsfile
      Acquired master cache lock.
      [CE47F913B3A5D3AC403DD8A225DB0EACDEBF7619-myproduct-myuser] $ "C:\Program Files\TortoiseHg\hg.exe" --config auth.jenkins.prefix=* --config ******** --config ******** --config "auth.jenkins.schemes=http https" pull
      pulling from http://myserver/hg/myproduct/
      abort: keyring: http authorization required but program used in non-interactive mode
      ERROR: Failed to update D:\workdir\.jenkins\hgcache\CE47F913B3A5D3AC403DD8A225DB0EACDEBF7619-myproduct-myuser
      Master cache lock released.
      ERROR: Failed to use repository cache for http://myserver/hg/myproduct/
      [workspace@script] $ "C:\Program Files\TortoiseHg\hg.exe" --config auth.jenkins.prefix=* --config ******** --config ******** --config "auth.jenkins.schemes=http https" pull --rev default
      pulling from http://myserver/hg/myproduct/
      abort: keyring: http authorization required but program used in non-interactive mode
      ERROR: Failed to pull
      ERROR: Failed to pull
      ERROR: Maximum checkout retry attempts reached, aborting
      Finished: FAILURE
      

      I did change the credentials in the credential settings properly.

      Please contact me in case of missing information.

      I guess it's something with cashed credentials by hg.exe and a user confirmation for the change of the credentials.

            Unassigned Unassigned
            chrisfetz Christoph Fetzer
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: