Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-9679

Jenkins2Tekton- Add ingestion of installed shared libraries

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • AI
    • None
    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • 2
    • Pipelines Sprint CrookShank 45, Pipelines Sprint CrookShank 46

      Story (Required)

      As a developer trying to successfully translate shared libraries methodsĀ  I want to read the installed shared libraries on a jenkins instance.

      In order to reliably convert an unknown method sourcing in a git repo shared library, I want to know the url for that repo containing the groovy source code.

      Background (Required)

      Jenkins2Tekton toll converts jenkinsfiles into valid tekton resources

      Out of scope

      building a separate tableĀ  for each customer upon deployment. the shared libraries shall be ingested into an already existing table.

      Approach (Required)

      use Jenkins-python package to pull info from an accessed instance.

      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

              rh-ee-ngelman Naomi Gelman
              rh-ee-ngelman Naomi Gelman
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: