Skip to content

Working Travis build #850

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

Closed
wants to merge 36 commits into from
Closed

Conversation

asbjornu
Copy link
Member

This PR completes the Mono support started in #816 and contains fixes all over the place to achieve a working build on Travis. Most tests are executed and succeed, but some tests using the ShouldMatchApproved() extension method from Shouldly had to be ignored, since they fail due to missing source information.

If Shouldly gains Mono .mdb symbol support, these tests can be un-ignored and the Travis (Linux) build of GitVersion should be on par with Windows and we should be in a great place to ensure Unix, Linux and Mono compatibility going forward.

After merging this, a Travis build badge like this can be added to the README:

Build Status

asbjornu added 30 commits April 27, 2016 17:02
Use lowercase `b` in `build` for improved compatibility with case-sensitive file systems.
Base the current directory of the documentation tests on the location of the test assembly instead of `Environment.CurrentDirectory`.
Add 'NoMono' category to AssemblyInfoBuilder tests since source information is not available to `ShouldMatchApproved()` on Mono.
Deleted test that effectively only tested the ProcessHelper; not GitVersion.exe, as it appeared to.
Deleted ProcessHelper and replaced usage with the one from GitTools.Core.
… reintroduce the NuGet dependencies to System.*
@asbjornu
Copy link
Member Author

Hm, why isn't AppVeyor building this, by the way?

@gep13
Copy link
Member

gep13 commented May 1, 2016

@asbjornu good question. @JakeGinnivan any ideas?

@asbjornu
Copy link
Member Author

asbjornu commented May 3, 2016

@gep13 My guess is that since the branch feature/mono-support was merged in f4795ff and this PR is based off of the same branch, AppVeyor believes that no build is required. I can create a new branch to create a new PR from, perhaps?

@asbjornu asbjornu mentioned this pull request May 10, 2016
@asbjornu
Copy link
Member Author

Closing in favor of #856, which is being built by AppVeyor right this moment.

@asbjornu asbjornu closed this May 10, 2016
@asbjornu asbjornu deleted the feature/mono-support branch May 13, 2016 07:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants