Download to read offline
Uploaded byGary Park
Having your cake, and eating it too!
Cake is a cross-platform build automation system with a C# DSL designed for tasks like code compilation, file management, and testing. Its main philosophies focus on being non-intrusive, highly configurable, and ensuring consistent behavior across different environments. The document outlines typical build workflows and provides various resources for further learning about Cake.
SoftwareâŚ
More Related Content
Having your cake, and eating it too!
- 1. Having your Cake,and eating it too! Gary Ewan Park Email: gep13@gep13.co.uk Twitter: @gep13 Web: http://www.gep13.co.uk
- 2.
- 5. A Definition⌠âCake (C#Make) is a cross platform build automation system with a C# DSL to do things like compiling code, copy files/folders, running unit tests, compress files and build NuGet packages.â Reference ď§ http://cakebuild.net/
- 6. Okay, but whydo I need it?
- 7. What are themain philosophies of Cake? ⢠Non intrusive ⢠It should âjustâ work ⢠Be highly configurable ⢠Replace the parts that you donât like ⢠Easy to implement your own tools ⢠No tools should be checked into your repository ⢠Should behave the same way regardless of ⢠Operating System ⢠Environment
- 8.
- 9. Canât I justuse⌠MAKEFAKECMakeMSBuildNAntPsakeBau
- 10.
- 11. Typical Build Workflow Clean Build UnitTests (NUnit, xUnit, MSTest) Test Coverage StyleCop FxCop DupFinder InspectCode Package Publish Package Restore
- 12. Letâs bake someCake! Clean Build Unit Tests (NUnit, xUnit, MSTest) Test Coverage StyleCop FxCop DupFinder InspectCode Package Publish Package Restore
- 13. Demo 1 NuGet PackageRestore
- 14. Progress Check Clean Build Unit Tests (NUnit,xUnit, MSTest) Test Coverage StyleCop FxCop DupFinder InspectCode Package Publish Package Restore
- 15. Demo 2 Build theSolution
- 16. Progress Check Clean Build Unit Tests (NUnit,xUnit, MSTest) Test Coverage StyleCop FxCop DupFinder InspectCode Package Publish Package Restore
- 17.
- 18. Progress Check Clean Build Unit Tests (NUnit,xUnit, MSTest) Test Coverage StyleCop FxCop DupFinder InspectCode Package Publish Package Restore
- 19.
- 20. Progress Check Clean Build Unit Tests (NUnit,xUnit, MSTest) Test Coverage StyleCop FxCop DupFinder InspectCode Package Publish Package Restore
- 21.
- 22. Progress Check Clean Build Unit Tests (NUnit,xUnit, MSTest) Test Coverage StyleCop FxCop DupFinder InspectCode Package Publish Package Restore
- 23. Questions? Feel free toget in touch Email: gep13@gep13.co.uk Twitter: @gep13 Web: http://www.gep13.co.uk
- 24. Resources ⢠Cake Documentation ohttp://cakebuild.net/docs ⢠MS Dev Show Podcast Episode o http://msdevshow.com/2016/04/cakebuild-with-mattias-karlsson-and-gary-ewan-park/ ⢠Motz Codes Live: Continuous Integration for Libraries with Jon Dick aka Redth o https://www.youtube.com/watch?v=D0gWjHhJ3IU ⢠Source Code o https://github.com/cake-build/cake ⢠Blog Posts o Moving to Cake (C# Make) â Laurent Kempe http://laurentkempe.com/2016/04/05/Moving-to-Cake-CSharp-Make/
Editor's Notes
- #2Â Full disclosure, I am one of three maintainers of the Cake project on GitHub
- #4 Sorry, but we are not here to talk about Cake of the edible formâŚ
- #5Â Instead, we are here to talk about Cake, the cross platform build and orchestration tool. - Supports the most common tools out of the box - Cross Platform (Windows OS X Linux) - Open Source - Small but slowly growing - 387+ Pull Requests - 50 Contributors - About 38 third party addins
- #6Â Built using Roslyn, and the Mono Compiler, allowing execution on both Windows, OS X and Linux Script Processing to make sure things work the same on both
- #7Â Talk about compiling directly out of Visual Studio - You might run some Unit Tests after the build has completed - You might run some static analysis tools within Visual Studio - You might manually create and deploy a package once you know that everything works This is prone to human error, and not repeatable or maintainable as the complication of the application increases
- #10Â You can use any of these that you want. Fully agree with the concept of a polyglot developer, but from a strictly pragmatic point of view, writing a build script in the same language as you are developing, makes a lot of sense.
- #11Â Notice, how it is just C# We have a top level set of input arguments We setup some top level arguments that will be used in the rest of the script We start to define the Tasks that will make up the script
- #12Â - Directed acyclic graph