feat: Add Interactive mode with target selection

[Danielku15]

I confirm that the pull-request:

• Follows the contribution guidelines
• Is based on my own work
• Is in compliance with my employer

---

This PR contains a proposal how #1436 could be implemented. Structurally we should still discuss where what should go but it already gives a feeling on what a user gets with this change.

Current design decisions

• I opted to the SpecterConsole as proposed in the issue.
• I moved the InvokedTarget loading logic into the ExecutableTargetFactory
• I put the implementation of selecting targets into NukeBuild to allow people overriding and customizing it.
• I made the ExecutableTargets public so custom implementations can use it.
• For the sake of simplicity i did not move yet the console logic into the Terminal class.
• I tried to keep the target selection output close to what a user sees when executing --help

Any feedback is welcome to complete this change.

Demo

rider64_xcwuHlW2Dh.mp4

class Build : NukeBuild
{
    public static int Main() => Execute<Build>();

    public Build()
    {
        Interactive = true;
    }

    public Target Compile => t => t
        .Description("Compiles the project")
        .Executes(() => Log.Information("Compile target execute"));

    public Target Test => t => t
        .DependsOn(Compile)
        .Description("Executes all tests")
        .Executes(() => Log.Information("Test target execute"));

    public Target PrepareEnvironment => t => t
        .Before(Compile)
        .Description("Prepares your development environment with all dependencies.")
        .Executes(() => Log.Information("PrepareEnvironment target execute"));
}

[matkoch]

Should be reverted

[Danielku15]

From my side this change was intentional. To properly be able to override and customize OnNoTargetsSpecified() developers need access to the general list of targets which are there as option.

e.g. in some projects we'd like to only be able to have a "single target" selection as this fits the project setup better and would like to change the default "multi selection" implementation shipped in nuke.

As alternative I could pass the executableTargets a parameter to OnNoTargetsSpecified.

[ITaluone]

I wouldn't go for "automatically detect local terminal and execute the interactive mode when no parameters given".

I would rather add an option on nuke :setup as opt-in. Maybe not everyone wants to be forced into interactive mode, especially, when running .\build.cmd before runs the pipeline and suddenly it stays in interactive mode, waiting for user input.
(Can also be considered as a behavioral breaking change IMHO)

[Danielku15]

I wouldn't go for "automatically detect local terminal and execute the interactive mode when no parameters given".

@ITaluone I agree and there are some considerations around that in the proposal. One important detail in this implementation is: there is an additional --interactive parameter (or bool Interactive {get;set;}) which is default unset. With the current implementation you have following options as a developer/user:

• You set --interactive on the commandline to activate the mode.
• You can set this.Interactive = <your own check> in the constructor of your Build class to control things.
• You can override the OnNoTargetsSpecified method and trigger any custom logic.