Skip to content

As an User I want execution configuration separated from my pipeline definition, so I can reuse the pipeline definition for multiple configurations #7

@pvdissel

Description

@pvdissel

As an User
I want execution configuration separated from my pipeline definition
so I can reuse the pipeline definition for multiple configurations

Acceptance criteria

  • Should provide the configuration to the command
  • Should be in a simple key/value pair format

Out of scope

  • Verification that required key/value pairs for pipeline definition are provided

Implementation ideas:

  • Standard Java Properties format
  • Groovy ConfigSlurper
  • Own GroovyDSL like the Pipeline DSL

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions