Cake.Recipe seems to not find VSTests in Cake.VsMetrics, see conversation here.

As discussed here:

http://stackoverflow.com/questions/41722455/how-to-launch-html-report-from-cake-build

/cc @devlead

As something might go wrong, and you need to push the changes locally.

Both the full set of releasenotes, and those contained within a specific release.

Once it is released. It is the last addin which isn't compatible with 0.18.0.

Not everyone will have one of these, but InspectCode should still be ran.

When an error is detected in DupFinder or InspectCode, the idea is that the generated report is opened. However, this simply currently opens a Windows Explorer to the incorrect location.

Such as DupFinder, OpenCover, etc

Similar to what has been incorporated for Wyam.

As suggested based on looking at @mvput build script 👍

This will prevent the setup.cake file in each repo needing to be changed when new functionality is added.

To contain all the tools that are loaded by default

Otherwise, there is no point in doing it.

Simply put, don't want to have to use these any more.

Otherwise, changing the documentation folder is going to cause problems.

Right now, Cake.Recipe assumes that Source Files (for API generation) are always included, but this might not actually be required. For example, in the case of ChocolateyGUI.

It should be possible to override the default.

https://ci.appveyor.com/project/cakecontrib/cake-recipe/build/0.2.0.build.4#L203

Tasks are being skipped that shouldn't be. Suspect that IsMainRepository isn't working correctly.

Including what it can do out of the box, and the types of overrides that are expected.

As not everyone is using that yet.

Use https://www.myget.org/F/cake/api/v2 instead.

/cc @ferventcoder

Similar to the following:

ExcludeCodeRegionsByNameSubstring = new string [] { "DupFinder Exclusion" },

This will prevent the need for each project using Cake.Recipe to list out the environment variables, unless they are using custom ones.

When running Cake.Recipe on Travis, the following error occurs:

https://travis-ci.org/cake-contrib/Cake.Plist/jobs/209156414#L1435

Compiling build script...
Error: Cake.Core.CakeException: An error occurred while executing build script.
  at Cake.Scripting.Mono.MonoScriptSession.Execute (Cake.Core.Scripting.Script script) [0x0007f] in <077b4364678d402f9df8bb48e9f0a543>:0 
  at Cake.Core.Scripting.ScriptRunner.Run (Cake.Core.Scripting.IScriptHost host, Cake.Core.IO.FilePath scriptPath, System.Collections.Generic.IDictionary`2[TKey,TValue] arguments) [0x00314] in <78602f51bc554886aeaf7e173d0ce2e7>:0 
  at Cake.Commands.BuildCommand.Execute (Cake.CakeOptions options) [0x0002d] in <077b4364678d402f9df8bb48e9f0a543>:0 
  at Cake.CakeApplication.Run (Cake.CakeOptions options) [0x0001d] in <077b4364678d402f9df8bb48e9f0a543>:0 
  at Cake.Program.Main () [0x000dc] in <077b4364678d402f9df8bb48e9f0a543>:0

I have been able to reproduce this error by compiling and running Cake on an Ubuntu VM, using JetBrains Rider. The issue comes down to the Cake.AppVeyor addin.

Now, some of you might be thinking, why are you using the Cake.AppVeyor addin when you are running on Travis, and this is due to the fact that you can't conditionally reference an addin, so it has to be included.

While debugging, it is the following method in the Cake.AppVeyor addin that is causing the problem:

Which reports the following error message:

System.Nullable [System.Int32] is not a supported constant type

The suspicion is that something in the Mono Compiler for Cake is either confused, or does not support what this method is trying to do.

var rootDirectoryPath         = MakeAbsolute(Context.Environment.WorkingDirectory);
var solutionFilePath          = "./Source/Cake.Gem.sln";
var sourceDirectoryPath       = "./Source";
var solutionDirectoryPath     = "./Source/Cake.Gem";
var title                     = "Cake.Gem";
var resharperSettingsFileName = "Cake.Gem.sln.DotSettings";
var repositoryOwner           = "cake-contrib";
var repositoryName            = "Cake.Gem";
var appVeyorAccountName       = "cakecontrib";
var appVeyorProjectSlug       = "cake-gem";

Many of these can be inferred from the combination of the Project Name and Source folder.

These should be allowed to be set to something else, but by default, let's infer them.

While trying to use Cake.Recipe on the ChocolateyGUI project, there were some issues with parsing of the Project Files, which is required for copying output files to the correct locations.

Some required information was missing, and as a result, errors were being thrown. Cake.Recipe should handle this a bit more gracefully.

For certain tasks it might be helpful if a log of the build was stored for further processing (eg. I'm currently working on a Cake Addin for writing code analysis issues as comments to pull requests).

The default should be to try all publishing steps (assuming they are required) but it should also be possible to override these steps.

var sendMessageToGitterRoom = true;
var sendMessageToSlackChannel = true;
var sendMessageToTwitter = false;
var sendMessageToMicrosoftTeams = true;

This can be inferred from whether the environment variables have been set

This should be included in the repository

To contain all the addins that are loaded by default

VS test can be used instead of MS test and an added benefit is that VS test can be used with OpenCover while MS test cannot.
MS test in your testing.cake does not work with OpenCover (there's a TODO comment). When I add VS test, I will make sure it works with OpenCover.

Edited to more clearly reflect what I was trying to say