Skip to content

Evaluate and redesign the make all workflow to reduce implicit side effects and improve target clarity #63

@dkruces

Description

@dkruces

Problem

The current make all behavior in kdevops implicitly triggers various setup and build actions depending on selected Kconfig options. This leads to:
Non-obvious execution paths where behavior changes based on configuration, not user intent.
Heavy unintended operations (e.g., mirror installation, environment provisioning, guest bringup).

Should make do work automatically, or only when explicitly instructed to?

Task

Refactor make all target:
Explore and define a clearer, more explicit Make invocation model that:
Reduces automatic side effects when running make.
Encourages users to run meaningful, high-level targets explicitly.
Makes workflows easier to understand for both humans and automated tooling.

Proposal:

  • make (all): Do nothing and/or create environment files such as extra_vars.yaml, .config, ansible.cfg, hosts, etc
  • make env: Create environment
  • ...

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions