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

Jenkins2Tekton converter- improve DB content

XMLWordPrintable

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

      None

      Show
      None
    • False

      Story (Required)

      filter existing content of the RAG, remove unrelated docs.

      Research for relevant Jenkins documentation, examples.

      ensure the general data is being stored in a separate table when running ingestion.

      make a new image containing the updated db, and upload to quay

      ----------------------------------------------------------------------------------------------

      ensure all personal data scraped from the instance is being stored in a second table in RAG once the access is given.

      edit the main logic so that scraping shall happen as soon as credetials are given.

      Background (Required)

      improving the content of the RAG may significantly improve quality of conversions. RAG currently contains mainly info for tekton, but not on Jenkins, which is crucial as this is the strating point. data on structure of the pipeline, common use cases and  examples will improve LLMs understanding on what should be done.

      Out of scope

      testing the real impact of the change.

      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

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

                Created:
                Updated: