Stored git credentials not used when submodule is updated

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      1. Configure a git project that uses a remote and submodule URL of the form https://
      2. Ensure credentials added to Jenkins
      3. Add advanced submodule behaviors with no options selected
      4. First build (where repo is cloned) pulls the submodule correctly
      5. Subsequent builds fail authorization on the submodule part (possibly submodule update if this is being used)

        1. screenshot-1.png
          25 kB
          Mark Waite
        2. Screen Shot 2016-07-08 at 09.52.58.png
          146 kB
          Giovanni Gargiulo
        3. Screen Shot 2016-07-08 at 10.09.17.png
          98 kB
          Giovanni Gargiulo

            Assignee:
            Unassigned
            Reporter:
            Steven Shipton
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: