Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
pvdissel opened this issue Aug 17, 2013 · 0 comments
Open

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

pvdissel opened this issue Aug 17, 2013 · 0 comments
Labels
story

Comments

@pvdissel
Copy link
Member

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
story
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pvdissel