Skip to content

Prevent removing all jobs if pipeline definition was not found by default #35

@hlubek

Description

@hlubek

Scenario:

  • prunner is started with definitions and jobs are run
  • prunner is started with a wrong path / pattern and no definitions are found
  • all previous jobs are removed

We should guard against this by not removing jobs for missing pipeline definitions by default.
There could be a flag to configure the cleanup of jobs with a missing definiton (e.g. remove, retention).

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions