Story (Required)

change the way input is given to the tool:

1. read all current pipelines on the instance
2. list the full path for each of the pipelines to the user
3. (user provides path for the target jenkinsfile)
4. run conversion

this becomes an interactive session once access to the instance in given.

• if given string is not one of the pathslisted- throw an informative error
• when listing, print all files recursively 
• make sure the conversion still happens right after user input

Background (Required)

In order to provide a more friendly using experience, We want to change the way input is given to the tool. currently, in order to run the script, a path to the location of the jenkinsfile is provided in the cmd. listing all existing pipelines on the instance will allow the user to choose more comfortably the specific job to translate.

Out of scope

Approach (Required)

<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

Acceptance Criteria (Mandatory)

<Describe edge cases to consider when implementing the story and defining tests>

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met