-
Notifications
You must be signed in to change notification settings - Fork 654
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
Unlist GitVersionTask 5.1.3 ? #2125
Comments
@arturcic is this something you have the ability to do? |
@dazinator I'm planning to release tomorrow or on Monday version 5.1.4 |
Ah ok. Probably for th ebest because even after downgrading to 5.1.2 of gitversiontask - that just gives me a different bug with a locked file: https://ci.appveyor.com/project/dazinator/dotnet-glob/builds/30988665 ! Fingers crossed for 5.1.4 haha |
Hmm.. building locally with GitVersionTask 5.1.4-beta1.177 nuget package added to my csproj results in lots of errors:
If this is going to be released tomorrow as 5.1.4 - i'm a little worries :-/ |
I think that is because of this c602fbb |
I can revert it and if you can check it's working |
ah right! Ok yeah sure |
Pushed, when it's ready would you mind checking the version and confirm it is fixed? |
Ok, will do |
waiting for a nuget package to appear for this build: 5.1.4-beta.1+179 |
It's pushed to nuget.org and I guess to AppVeyor as well |
The appveyor feed is usually pretty quick at showing the new package, so just thought it was odd that its not there. I know Nuget,org can take a while haha |
Ok its appeared on nuget.org |
Nope with this version I get a different error:
My project (DotNet.Glob) supports a large array of target frameworks like so: <TargetFrameworks>netstandard1.1;netstandard2.1;netcoreapp2.1;net45;net46;net4</TargetFrameworks>
Previously I was using GitVersionTask
However all of a sudden, the AppVeyor build starting breaking: https://ci.appveyor.com/project/dazinator/dotnet-glob/builds/30988139 I thought perhaps updating GitVersion to latest version would help, and thats why I am not attempting to this, but no avail yet. As to why my builds have started failing with "4.0.1-beta1-65" - I can only assume there must be some AppVeyor image change which has introduced an issue that didn't exist before - or that somehow the commit history of my repository is now causing this bug to exhibit that didn't before. Who knows, but perhaps this is an issue only local to my project. |
In my AppVeyor build I am first doing an ordinary I'm going to try just upgrading i.e AppVeyor.yml
and
|
btw, now we also publish to GitHub Package Repository |
Ok that worked: https://ci.appveyor.com/project/dazinator/dotnet-glob/builds/30989316 So I have to remain on GitVersionTask |
@arturcic - right I did some digging and I have discovered the source of the problem. GitVersionTask 5.1.4-beta1.177 (the one prior to your revert) does indeed work as long as you use a stable dotnet sdk like 3.1.101, or 3.0.100 to build it e.g: {
"sdk": {
"version": "3.0.100"
}
} and
In my case, I have dotnet sdk 3.1.200-preview-014883 installed (I think this must have been installed by VS - Prerelease channel update), and this causes the problem when I build from VS locally, as GitVersionTask can't resolve its desired MSBuild assembly. I just need to add a global.json to pin my sdk version for now. I tested with beta.179 also but beta 179 definatelt seems broken. Even if I build that with a stable SDK i get this:
So with that in mind, would you mind reverting your revert? .. and sorry for the trouble! |
sure |
when the new build is ready, could you once again validate it's working with the global.json fix again? |
@dazinator can you check 5.1.4-beta1.181? |
Yep sure. By the way the global.json seems to fix the issue for So there seems there will always be an issue for VS builds given the way things currently work, in that, GitVersionTask will only work with specific versions of VS, and if you upgrade your VS to a new preview that is using a newer MSBuild then GitVersionTask builds may start failing - even if you add a global.json. To that end, we should probably document which versions of VS can be used with GitVersionTask for each stable release, and making it very clear that if you use newer versions of VS, your mileage may vary. |
Do you think we need to include this in the release notes of the nuget package? or the one on GitHub |
Tested with VS2019 Community Preview and also VS2019 Professional. Both fail with: Severity Code Description Project File Line Suppression State
|
Are there any options we can fix it in VS? |
Yeah that would be handy. Or perhaps we link to a doc that has a matrix with GitVersionTask version and VS versions it runs in, which we could start maintaining as of the next release. The problem is, it really requires us to test the GitVersionTask with various VS versions to achieve this - or perhaps, test GitVersionTask with various MSBuild versions. I know that you can write tests that utilise a particular version of MSBuild so its faesilbe we could write tests for GitVersionTask that excercise it using a variety of MSBuild versions, known to be associated with particular VS versions, then we say if you are using a VS version that doesn't use one of the following MSBuild versions then your mileage may vary. Needs some thought. |
Ok, when you have some ideas to share, please let us know. Do you think having this issue, we can release version 5.1.4? |
I don't think so, but there are some things we can try that might sort it. Like this So places like here: https://github.com/GitTools/GitVersion/blob/master/src/GitVersionTask.MsBuild/GitVersionTaskBase.cs#L6 Came accross that discussion here: dotnet/msbuild#2111 I am willing to give this a go. Where should i be branching from these days - do I just create a new branch from master and submit a PR? or is there a develop branch that I can't see for beta stuff? |
I usually use my fork and submit a PR |
you need dotnet format global tool and run it like |
geees... does github now have its own build system - what's going on here: https://github.com/GitTools/GitVersion/actions/runs/43623597/workflow Not another one, pleaseeeee haha |
One thing we could do to catch issues earlier.. We could add a check to the CI build that does an Here is me reproducing this issue locally using msbuild:
|
I haven't been able to get to the bottom of this error to do with being unable to load System.Runtime.Loader. |
You can also run |
Yep - I figured that one out just before I was about to bother arturcic again. |
Going to close this and create seperate issues for things I've found. |
GitVersionTask 5.1.3 has a pretty serious bug that breaks appveyor builds. I appreciate this won't necessarily impact other build systems, but given that AppVeyor it s pretty common one, it might be a good idea to unlist GitVersionTask 5.1.3 on nuget so people updating to latest stable (like I just have) don't end up hitting this issue. At the moment we have yet to release a fixed version (5.1.4) so 5.1.3 is the latest stable version on NuGet.
Here is a build showing the newtonsoft problem: https://ci.appveyor.com/project/dazinator/dotnet-glob/builds/30988507#L294
The text was updated successfully, but these errors were encountered: