Question 1

How do I pass custom command-line arguments to my Bullseye targets?

Accepted Answer

Use a command-line parsing package like System.CommandLine to handle custom arguments, then pass only valid ones to Bullseye. The README provides examples with System.CommandLine and McMaster.Extensions.CommandLineUtils for seamless integration.

Question 2

Bullseye or Cake Build: which should I use for .NET automation?

Accepted Answer

Bullseye is lighter and more code-centric, ideal for simple to medium workflows where you prefer writing C#. Cake offers a richer ecosystem with more built-in tasks and plugins. Choose Bullseye for flexibility, Cake for extensive community support.

Question 3

Can Bullseye run targets in parallel?

Accepted Answer

Bullseye does not natively support parallel execution of targets; it runs them sequentially based on dependencies. For parallelism, you need to implement it within target actions, such as using Task.Run or similar .NET concurrency features.

Question 4

How to integrate Bullseye with GitHub Actions?

Accepted Answer

Call Bullseye targets from GitHub Actions by adding a step that runs 'dotnet run --project Targets -- targetName'. This allows you to incorporate Bullseye workflows into CI/CD pipelines without extra configuration.

Question 5

What's the best way to handle errors in Bullseye?

Accepted Answer

Use the RunTargetsAndExitAsync method with custom exception handling, such as catching ExitCodeException from SimpleExec. This lets you log errors or perform cleanup before exiting, as shown in the quick start code.

Question 6

How to create a dry run with Bullseye?

Accepted Answer

Use the --dry-run option when executing Bullseye from the command line to list the targets that would be executed without running them. This helps verify the dependency graph and execution order beforehand.

Bullseye

What is Bullseye?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions