English | 中文

"FlubuCore - Fluent Builder Core" is a cross platform build and deployment automation system. You can define your build and deployment scripts in C# using an intuitive fluent interface. This gives you code completion, IntelliSense, debugging, FlubuCore custom analyzers, and native access to the whole .NET ecosystem inside of your scripts.

FlubuCore offers a .net (core) console application that uses power of roslyn to compile and execute scripts. Above example can be run from console with:

• FlubuCore runner flubu.exe Default
• FlubuCore dotnet cli tool dotnet flubu Default
• FlubuCore global tool flubu Default

• Intuitive an easy to learn. C#, fluent interface, and IntelliSense make even most complex script creation a breeze.

context.CreateTarget("Example")
  .DependsOn(fetchBuildVersionTarget)
  .AddTask(x => x.CompileSolutionTask())
  .AddTask(x => x.PublishNuGetPackageTask("packageId", "pathToNuspec"))
      .When(c => c.BuildSystems().Jenkins().IsRunningOnJenkins);

• Large number of often used built-in tasks like e.g. running tests, managing IIS, creating deployment packages, publishing NuGet packages, docker tasks, executing PowerShell scripts and many more.

context.CreateTarget("build")
   .AddTask(x => x.GitVersionTask())
   .AddTask(x => x.CompileSolutionTask("MySolution.sln").BuildConfiguration("Release");

context.CreateTarget("run.tests")
   .AddTask(x => x.XunitTaskByProjectName("MyProject").StopOnFail())
   .AddTask(x => x.NUnitTask(NunitCmdOptions.V3, "MyProject2").ExcludeCategory("Linux"))
   .AddCoreTask(x => x.CoverletTask("MyProject.dll"));

• Execute your own custom C# code.

context.CreateTarget("MyCustomBuildTarget")
     .AddTask(x => x.CompileSolutionTask())
     .Do(MyCustomMethod)
     .Do(NuGetPackageReferencingExample);

• assembly references and nuget packages are loaded automatically when script is used together with project file. When script is executed alone (for example when deploying with FlubuCore script on production environment) references can be added with attributes.

[NugetPackage("Newtonsoft.json", "11.0.2")]
[Assembly(".\Lib\EntityFramework.dll")]
public class BuildScript : DefaultBuildScript
{
   public void NuGetPackageReferencingExample(ITaskContext context)
    {
        JsonConvert.SerializeObject("Example");
    }
}

• Easily run any external program or console command in your script.

context.CreateTarget("Run.Libz")
    .AddTask(x => x.RunProgramTask(@"packages\LibZ.Tool\1.2.0\tools\libz.exe")
        .WorkingFolder(@".\src")
        .WithArguments("add")
        .WithArguments("--libz", "Assemblies.libz"));

• Pass command line arguments, settings from json configuration file or environment variables to your script.

public class SimpleScript : DefaultBuildScript
{
   [FromArg("sn", "If true app is deployed on second node. Otherwise not.")]
   public bool deployOnSecondNode { get; set; }


    protected override void ConfigureTargets(ITaskContext context)
    {
        context.CreateTarget("compile")
           .AddTask(x => x.CompileSolutionTask()
               .ForMember(y => y.SolutionFileName("someSolution.sln"), "solution", "The solution to build.")); 
    }
 }

 flubu.exe compile -solution=someOtherSolution.sln -sn=true

• Extending FlubuCore fluent interface by writing your own tasks within FlubuCore plugins.

  public class ExampleFlubuPluginTask : TaskBase<int, ExampleFlubuPluginTask>
  {
      protected override int DoExecute(ITaskContextInternal context)
      {
          // Write your task logic here.
          return 0;
      }
  }

• Growing list of FlubuCore plugins complements built in tasks.

• Asynchronous or parallel execution of tasks, target dependencies and custom code.

  context.CreateTarget("Run.Tests")
      .AddTaskAsync(x => x.NUnitTaskForNunitV3("TestProjectName1"))
      .AddTaskAsync(x => x.NUnitTaskForNunitV3("TestProjectName1"))
      .AddTaskAsync(x => x.NUnitTaskForNunitV3("TestProjectName3"));

• Override existing options or add additional options to tasks through console

  context.CreateTarget("Example")`
     .AddCoreTask(x => x.Build("MySolution.sln").Configuration("Release"); 

  flubu example --configuration=Debug

  flubu would execute dotnet build MySolution.sln --configuration Debug

• Full .NET Core support including the global CLI tool

  dotnet tool install --global FlubuCore.GlobalTool
  flubu compile
  

• FlubuCore interactive mode which offers target tab completition, options tab completition, toogle targets/options, executed commands history. It is also possible to execute external commands and operable programs. For some of them FlubuCore offers tab completion with help displayed at the bottom of console out of the box(such as dotnet, git..)

• Possibility to test and debug your build scripts.

  context.WaitForDebugger();

• Easily automate deployments remotely via the FlubuCore Web API.

• Possibility to use FlubuCore tasks in any other .NET application.

• Improved developer experience with FlubuCore custom analyzers.

Using FlubuCore is straightforward and very simple :-) It is also fully and throughly documented.

The Getting Started chapter in FlubuCore Documentation will help you set up your first FlubuCore build in no time.

A comprehensive list of features that FlubuCore has to offer with descriptions can be found in the Build Script Fundamentals chapter.

Once you have your build and deployment scripts defined, the following Wiki chapters will explain how to run them:

• For .NET Framework projects use FlubuCore.Runner
• For .NET Core projects use FlubuCore CLI global tool

Aside from the detailed Wiki FlubuCore comes with example projects that reflect real-life situations. The examples can be found in the separate Examples repository.

These examples will help you to get quickly start with FlubuCore:

• .NET Framework build example

• .NET Core build example

• Deployment script example

Please see CONTRIBUTING.md.

• Spread the word about the project.
• If you like the project don't forget to give it a star so that the community get's bigger.
• Improve documentation.
• Report, fix a bug.
• Implement a new feature.
• Discuss potential ways to improve project.
• Improve existing implementation, performance, etc.

Changes with description and examples can be found in Changelog

You can see FlubuCore roadmap by exploring opened Milestones.

Thank's to Comtrade for supporting us.

• Special thanks to @ironcev for greatly improving readme and for giving some valuable advices.
• Special thanks to @alexinea for translating whole documentation to Chinese.