DuckDefender
Deployment Options

Deployment Options

Agent DuckDefender from Flyingduck can be deployed in two ways: either by integrating the DuckDefender agent file into your workflow or by using the On-premise Runner.

  • Workflows:
    Workflows are action jobs set up in version control systems to execute specific tasks when certain criteria are met. However, they consume build minutes, and once depleted, code scans cannot run. To address this limitation, runners are introduced.

  • Runner:
    Runners function like virtual machines (VMs) that perform code scans within your environment. The results are then posted to the portal for users to view. This method doesn’t consume build minutes since it operates on your infrastructure, ensuring that the code remains within your organization.

  • Command Line:
    CLI is a simple docker command that will quickly scan your repository for issues without setting up any additional workflows.The scan will always run against the latest commit present in the cloned repository at the time of execution. Make sure your repository is up to date before running the scan to get the most accurate results.This integration is perfect for command-line environments, CI servers, or any situation where you prefer immediate, on-demand checks without integrating into your source control system.