Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Not A Defect
    • Component/s: git-plugin
    • Labels:
    • Environment:
      Windows 2016 for both mast and slave. Alternate credentials for git
    • Similar Issues:

      Description

      Overnight, with no changes, an authentication failure occurred which prevented us from using the alternative credentials within VSTS. I made sure that the creds in both Jenkins and VSTS are the same. When I try to manually login on git from the master, I receive this error:

      fatal: Authentication failed for 'https://prod1.visualstudio.com/_git/prodscripts/'

      Within Jenkins, I have this error on a job:

      Failed to connect to repository : Command "git.exe ls-remote -h https://prod1.visualstudio.com/_git/prodscripts HEAD" returned status code 128:stdout:stderr: fatal: Authentication failed for 'https://prod1.visualstudio.com/_git/prodscripts/'

      I made sure everything is also up to date. I'm at a little bit of a loss on this one.

        Attachments

          Activity

          Hide
          markewaite Mark Waite added a comment -

          Chris Huddleston you'll get better results requesting help from a larger group than the few people that watch the bug reports in the Jira project for the git plugin.

          The Jenkins users mailing list and the Jenkins chat channels all have many more readers and many more contributors than the number of people that watch git plugin bug reports.

          When I was using Visual Studio alternate credentials, there were times that the alternate credentials were disabled by the Visual Studio Team System server. I don't if that was due to detected attacks or due to authentication failures or due to expiration of a time limit on the alternate credentials.

          Ultimately, I stopped using alternate credentials because I was tired of adapting to the times when they became disabled. I believe Visual Studio provides authorization tokens that can be generated and used as "single purpose credentials". You may want to investigate those.

          Show
          markewaite Mark Waite added a comment - Chris Huddleston you'll get better results requesting help from a larger group than the few people that watch the bug reports in the Jira project for the git plugin. The Jenkins users mailing list and the Jenkins chat channels all have many more readers and many more contributors than the number of people that watch git plugin bug reports. When I was using Visual Studio alternate credentials, there were times that the alternate credentials were disabled by the Visual Studio Team System server. I don't if that was due to detected attacks or due to authentication failures or due to expiration of a time limit on the alternate credentials. Ultimately, I stopped using alternate credentials because I was tired of adapting to the times when they became disabled. I believe Visual Studio provides authorization tokens that can be generated and used as "single purpose credentials". You may want to investigate those.

            People

            • Assignee:
              markewaite Mark Waite
              Reporter:
              huddles18 Chris Huddleston
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: