multibranch builds with visual studio incorrectly handles branches with a slash

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

XMLWordPrintable

      When a multibranch build is built using a branch with a slash (e.g. feature/xyz), the workspace folder is created using the encoded name "feature%2Fxyz". When visual studio sees this while resolving paths , it takes "%2F" as a "/".

      So visual studio thinks there is supposed to be a subfolder under "feature" called "xyz".This causes the build to fail if there are relative paths to files that devenv attempts to resolve

            Assignee:
            Stephen Connolly
            Reporter:
            Wesley Eledui
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: