-
Notifications
You must be signed in to change notification settings - Fork 35
Automated versioning for dll #96
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
Comments
I've tested GitVersionTask on Linux and its currently buggy hopefully GitTools/GitVersion#1511 will fix it until then I'm hesitant to put it in ModTek, do we only use Windows for releases? |
I don't know what @mpstark uses, but I was building MT on MacOS for the last half year. |
This seems like on *nix it could be solved with a small git commit hook and regex. I suspect powershell can do it easily, too, but I don't know anything about that. |
I rather wait for GitVersionTask to be fixed, it also does smart increments, e.g. if you have 1.0.3 tagged, but have untagged commits afterwards on your current branch, it will compile as 1.0.4. It is the ultimate tool for building these things. Issue is that GitVersionTask isnt using the git nuget package, but packaging libgit itself. That will hopefully change soon. In any case, I'll create a PR for @janxious to test on mac! |
@jo @mpstark https://github.com/orgs/BattletechModders/teams/btml-modtek does not have access to ModTek, couldnt push my branch :( |
@CptMoore Should be fixed now. Sorry about that. |
For MechEngineer, I use GitVersionTask to do automated assemblyinfo versioning as part of building. Just tag the HEAD and rebuild the dll. Works great, could quickly port it to ModTek.
The text was updated successfully, but these errors were encountered: