-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
URL for Bitbucket cloud #185
Comments
Is the PDB loaded for the module (you can see loaded PDBs in Debug > Windows > Modules)? |
Just commenting to say this was at work and I haven't had chance to get round to recreating the test case (yet). |
Thanks @tmat I didn't know about that window. I have made some progress. The PDB was not loaded. I have added
to my csproj file and they are now getting loaded. So onto the next issue, which is that VS cannot find the source files. I get some output like the following. VS is first looking for a file path on the build server (which doesn't work of course) and then tries SourceLink
We are building our own NuSpec files and packing them using NuGet.exe, but the repository URL in the file looks good to me (apart from the redirect problem I mentioned in the initial report):
|
Further update. I checked the json doc that is created by SourceLink, and it contains a URL of the form
I've tried adding a path to a cs file on the end of that URL in the browser and that does indeed get me the raw source code. For Info: The Bitbucket URL format is documented here https://confluence.atlassian.com/bitbucket/hyperlinking-to-source-code-in-bitbucket-824476709.html so it looks correct. Here is the code that builds the link https://github.com/dotnet/sourcelink/blob/master/src/SourceLink.Bitbucket.Git/GetSourceLinkUrl.cs |
I've tried many things now. Currently I have the following in the csproj file
and in the nuspec file
The project is being built with
(Here, CreateSymbols is just a flag that is passed onto our CI targets that ensures that the -Symbols option is not passed to NuGet.exe, it's not relevant to this discussion. Likewise, CreatePackages is a flag that causes our targets to invoke 'nuget.exe pack'). Checking the log on Bamboo, I can see this:
Which probably explains why it is not working. At this point I'm stuck. |
Encountering the same behaviour with 1.0.0-beta2-19351-01. Same configuration is working fine locally. On build machine, I have the warning : And here are the logs form diagnostic dotnet build
The generated .nuspec contains correct informations, but not the dll. |
I think I have found the problem. It is linked with bamboo build server, me and @PhilipDaniels are both using it.
The problem lies here for me :
|
Adding git remote set-url origin https://bitbucket.honeywell.com/scm/datarelay/tcc2.git after source code checkout seems to be enough to solve this problem |
We have made several improvements and fixes in BitBucket support. Please try the latest package (version 1.0.0-beta2-19554-01). Feel free to reopen this issue if you find any problems with the package. |
Trying to get SourceLink working with our Bitbucket cloud hosted solution. Our urls are of the form
At least, I can type that into a browser window, but it will redirect me to
Anyway, I have published a package but when I try to step into it in VS2017 15.8 nothing happens - no error message, no dialog, it just steps over the method call.
Is this URL format supported? I was reading #31 and it links to this bit of code https://github.com/ctaggart/SourceLink/blob/master/SourceLink.Create.CommandLine/BitBucketServerUrlConverter.cs which does not match our URLs.
I have the latest preview version of SourceLink for Bitbucket installed.
The text was updated successfully, but these errors were encountered: