Set up Travis CI yaml

[ferventcoder]

Official docs http://docs.travis-ci.com/user/languages/csharp/

Some references that are likely outdated (but might prove helpful):

• http://stackoverflow.com/a/16751773/18475
• http://pseudomuto.com/development/walkthroughs/2013/08/13/continuous-integration-for-net-with-travis-ci-and-xunit/
• https://danlimerick.wordpress.com/2013/02/03/build-your-open-source-net-project-on-travis-ci/

[gep13]

For this one, do you already have a Travis account that you want the build to run under? If so, can you make others in the team have access? I have never looked at Travis, but more than happy to look at this.

[ferventcoder]

I do have a travis account. This would use mono to build. There are some examples of doing this out there.

[ferventcoder]

Just turned it on https://travis-ci.org/chocolatey/choco/

[gep13]

Nice one! I will take a look. Will have some reading to do for this one :smile_cat:

[gep13]

Have you given me any sort of permissions to the Travis site? I don't see anything immediately that says to create a new build configuration?

[ferventcoder]

Here's a pretty comprehensive answer http://stackoverflow.com/a/16751773/18475 - note we already have ./build.sh so we don't need to call xbuild directly.

[ferventcoder]

You create a .travis.yml file. It's that simple. Travis-CI is considered the first zero configuration build server.

[gep13]

ooo, interesting, didn't realise that. Cool, I will let you know if I have any questions.

[ferventcoder]

A couple of nice walkthroughs in case we run into speedbumps:

• http://pseudomuto.com/development/walkthroughs/2013/08/13/continuous-integration-for-net-with-travis-ci-and-xunit/
• https://danlimerick.wordpress.com/2013/02/03/build-your-open-source-net-project-on-travis-ci/

[ferventcoder]

Official docs http://docs.travis-ci.com/user/languages/csharp/

[ferventcoder]

The last is preferred, it's the most recent and likely the easiest to test.

[gep13]

@ferventcoder I have added a VERY basic travis.yml file into chocolatey/choco and issued it as a pull request, thinking that this would kick off a build in travis. However, nothing seems to be happening. Am I right in thinking that the file will need to exist on the master branch, before travis knows what to do with it, or rather, than it "should" be doing something?

[ferventcoder]

I left a comment over there for you. The name of the file must start with a dot.