Skip to content

Conversation

latkin
Copy link
Contributor

@latkin latkin commented Feb 4, 2015

CI builds everything in debug config today. I see a few problems with that, and only 1 potential benefit.

Cons

  • Causes tests to run more slowly
  • Prevents all tests from working (fsharpqa and ideunit tests trigger many bogus asserts)
  • Build output is slow/asserty, so we can't use it to run full local validation here.

Pros

  • Easier to debug if someone is testing the new feature/behavior
    • But to debug, user will still need updated sources...

Changing to release config means tests will execute faster (i.e. CI build will go faster), and CI output can be used to bootstrap full local validation by maintainers.

@dsyme
Copy link
Contributor

dsyme commented Feb 4, 2015

Fine by me. (nb. having switched to the paid account we may be able to configure a matrix of builds?)

@latkin latkin closed this in c023732 Feb 4, 2015
@latkin latkin added the fixed label Feb 4, 2015
@latkin latkin deleted the appveyor-release branch February 5, 2015 05:40
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