(#2400) Replace UppercuT with Chocolatey.Cake.Recipe #2706

These are no longer required, as all the functionality is now being provided by Chocolatey.Cake.Recipe.

Previously, the UppercuT build required that all tools were either already installed on the machine, or present in the lib folder of the repository. This strategy is no longer required, as the Chocolatey.Cake.Recipe already has the ability to download the tools when required as part of the build process.

Storing the NuGet.exe is in the repository is no longer required. This tool will be resolved, as required, when the build runs.

Chocolatey.Cake.Recipe is quite opinionated about the folder structure that is used when creating Chocolatey and NuGet packages. It expects all nuspec files to be stored in a folder structure like the following: - nuspec - chocolatey - nuget With the UppercuT build, this structure existed, just in a slightly different way. This commit updates the folder structure to be what is required.

This includes pinning to the currently supported version of Cake, 0.38.5, and also to include a cake.config file to allow overridding of the checks that Cake does of out of support addins (these are knowingly being overridden at the minute). The Cake bootstrappers that are being used in the Chocolatey GUI build have been copied over into this repository. Within the recipe.cake file, the project specific changes have been made, including which files should be signed, ILMerge'd, etc.

Rather than calling into UppercuT the build entry files, i.e. build.bat, etc, have been updated to call into Cake.

Cake outputs to a new file (and a lot to the terminal). This updates the script used for running the tests to default to the new location. We also update the Vagrantfile to silently absorb the output from the build script as it seems to output too fast for vagrant to handle consistently.

The folder structure has changed, as a result, changes to the build, as well as what parameters are passed into the build, need to be made to match the new way of doing things.

This will mean that the generated release notes are using the standard look and feel that we want for all release notes.

The strucutre of the code_drop folder has changed, and the docker portion of the build needs to be updated to reflect this new structure.

This NuGet package is no longer required, as the work that it was doing is now being handled within the Chocolatey.Cake.Recipe. i.e. the output from the different project types is now copied to the correct locations as part of the build process.

This is not currently being used, and can be removed as it will reduce maintenance overhead going forward.

A lot of the work that was previously being done in the TeamCity settings file is now done by the Recipe, and therefore can be removed.

In order to get the build to work correctly, we need to install a newer version of git on the build machine (this means using the backports registry) and also to install the .NET CLI.

In order for the Cake Build to correctly identify that it is running on GitHub Actions, in order to assert teh correct branch name to use the environment variables from the GitHub Actions build image have to be passed through to the execution of Docker. We don't need all the variables, just the ones used by Cake to make some assertions.

To account for the new way that things are executed under Chocolatey.Cake.Recipe.

The ordering of the tasks was thrown out a bit due to the introduction of the Prepare-NuGet-Packages and Prepare-Chocolatey-Packages tasks. This corrects that issue, and also maps all the required files

This will mean that Cake and the other tools/dependencies won't need to be resolved/downloaded each time.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

(#2400) Replace UppercuT with Chocolatey.Cake.Recipe #2706

(#2400) Replace UppercuT with Chocolatey.Cake.Recipe #2706

Commits on Jun 23, 2022