Cake
bullseye
Our great sponsors
Cake | bullseye | |
---|---|---|
13 | 4 | |
3,811 | 821 | |
0.8% | - | |
8.2 | 8.2 | |
2 days ago | about 15 hours ago | |
C# | C# | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Cake
-
Unpopular opinion: CI/CD engines are an awful idea
This is why 90-99% of our builds are done with Cake. It isolates all of it and you can run the build locally if you want.
-
Cake v2.3.0 released - New Command aliases, New .NET Workload aliases, improved global caching of scripts, bug fixes, and more.
A good starting point of you want to get started with Cake is our website at https://cakebuild.net/
-
Cake : A C23 to C99 transpiler
I don't think it will get too much confusion, but there is a build system called Cake: https://cakebuild.net/
-
Achieving single command Infrastructure deployment using PowerShell DSC.
You may use other tools too: psake, make, cake, fake or any other *ake you are familiar with. I look at them as a tools that make build tasks behind simple commands and help me answer: How did I run that code again?
-
.NET build tool using Bullseye and SimpleExec
NAnt was quite a popular build tool used by projects of all sizes targeting .NET Framework on Windows. I have written many complex build systems using NAnt in the past. But XML based DSL was quite clunky to use and maintain. Besides, it was always a daunting task to explain to a new dev on the team. With .NET Core/.NET becoming a cross-platform framework, CAKE and FAKE gained a lot of adoption providing a C# and F# based DSL for build tasks accordingly.
-
Nuke Build - best build automation system
Cake (C# Make) - simple, easy to set up, and with a lot of extensions scripting with C#.
-
Can Cake be used to build a .NET Core 3.1 console application for Windows, Linux and Mac... on a Windows machine?
I got the example and the answer I needed on this thread: https://github.com/cake-build/cake/discussions/3564
-
Creating reusable build scripts with NUKE components
For those not familiar with it, Cake is a build automation system with a C#-based DSL. It is based on the concept of tasks, which are small units of work, like restoring packages, building, or testing, which can have dependencies on, or trigger, other tasks.
-
A super simple make wrapper for docker/podman that runs all your targets in a container - just a utility I put together to make my life slightly easier, nothing fancy
Just a note: there's already a very active community of the same name for the build utility Cake.
-
A stupid simple make wrapper that makes my life easier
Looks interesting! Although the name clashes with Cake (C# Make) project which could be confusing - https://cakebuild.net/
bullseye
-
Do you know how I can execute these tasks parallely?E.g Task2 depends on Task1, Task3 depends on Task Task2, also Task 4 depends on Task1 but it not depends on Task2 and Task3. My execution time is 2 sec, I have to optimise it. Now I only call these tasks in await order e.g Await Task1(); ...
Checkout bullseye https://github.com/adamralph/bullseye
-
CAKE vs NUKE?
I used to use Cake and contributed but now bullseye is what makes sense https://github.com/adamralph/bullseye
-
What is the/your current/popular choice for dotnet c# scripting ?
I personally use Bullseye and SimpleExec instead of Nuke. I really like sticking to "normal" C#. I used Cake before but never liked it.
-
.NET build tool using Bullseye and SimpleExec
I personally advocate Bullseye in combination with SimpleExec as a build tool for .NET projects due to its sheer simplicity by providing a bare bones API to define the tasks and their dependent tasks in plain C# code. Both these libraries are build by Adam Ralph. It does not enforce any specific model or structure to write your build tasks. When someone runs through the build script, it is fairly straight forward to understand whats going on. We use this build tool setup for Marten for both local dev and CI build tasks and has worked well so far. Also many OSS projects have adopted it.
What are some alternatives?
NUKE - 🏗 The AKEless Build System for C#/.NET
ClearScript - A library for adding scripting to .NET applications. Supports V8 (Windows, Linux, macOS) and JScript/VBScript (Windows).
MSBuild - The Microsoft Build Engine (MSBuild) is the build platform for .NET and Visual Studio.
dartz - Functional programming in Dart
FAKE - FAKE - F# Make
UpdatR - Update tool for package reference and dotnet-tools.json
Psake - A build automation tool written in PowerShell
ScriptCS - Write C# apps with a text editor, nuget and the power of Roslyn!
Invoke-Build - Build Automation in PowerShell
dotnet-script - Run C# scripts from the .NET CLI.
Nake - Magic script-based C# task runner for .NET Core
simple-exec - 🏃 A .NET library that runs external commands.