-
Notifications
You must be signed in to change notification settings - Fork 654
Fix addin/tool versions #1340
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
Fix addin/tool versions #1340
Conversation
gep13
commented
Dec 6, 2017
- This will make the builds more reliable and repeatable
- This will make the builds more reliable and repeatable
@JakeGinnivan can you take a look at this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
Unfortunately I don't have permissions to merge it as long as a build fails. The failing AppVeyor build doesn't seem to be related to this change (it creates gitversion-4.0.0.fix.pre.addin.pre.tool.pre.versions.1.gem
and tries to upload gitversion-4.0.0.fix-addin-tool-versions.1.gem
)
@pascalberger yeah, that sounds like another bug that needs to be resolved. I can try to take a look at that later, but can't guarantee it :-( |
Looks good to me, but we can't release beta13/14 yet. I have been testing and had scenarios where it isn't picking up merge messages, I think we have a decent regression somewhere |
@JakeGinnivan ouch! Is this showing up in the tests, or just from your own testing? |
Just from my own testing. Also, there is a branch config inheritance issue.. See https://travis-ci.org/GitTools/GitVersion/jobs/312274320 - got stuck in a loop.. May take me a day or two, but I will try to add the tests and ensure we don't have those regressions. It would be handy if everyone could build and do some basic testing of master on their own code bases to see if there are issues |
Hopefully this should go green now, then can merge and we should be good to release beta.14 |
@JakeGinnivan looks like there is still an issue with the uploading of artifacts. |
Odd that it's the branch build failing but all others succeed. I recon we just merge. It's probably a gem precondition not creating it for that build |