Uploaded image for project: 'OpenShift Builds'
  1. OpenShift Builds
  2. BUILD-827

Onboard Robo-badger service to source-to-image product

XMLWordPrintable

    • False
    • None
    • False
    • Pipeline Integrations #3253

      Story (Required)

      <Describes high level purpose and goal for this story. Answers the questions: Who is impacted, what is it and why do we need it? How does it improve the customer’s experience?>

      Software production Cloud Workflow Product Configuration team strongly advice product teams to configure the Robo badger automation which can significantly speed up any small changes in release configuration.
      source-to-image is already onboarded to Honeybadger automation but it is missing Robo-badger service.

      Background (Required)

      <Describes the context or background related to this story>

      Robo-badger is a GitLab bot that allows users to automatically merge some merge requests without a review from release engineers if the changes present in the MR meet the requirements.

      Out of scope

      <Defines what is not included in this story>

      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>

      • Robo-badger service is successfully set up for the source-to-image product.

      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

              diagrawa Divyanshu Agrawal
              diagrawa Divyanshu Agrawal
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: