RE Pipeline Structure

Pipleline Structure

RE Dev and Release Pipelines are created based on the below structure

• Purpose

  • Build & Host the Component RPM's on Code changes

• Process

  • Prepare

    • Cleanup Workspace & RPM Dir
    • Install Dependencies (Eg: Python)

  • Checkout

    • Clone the source code in Jenkins workspace

  • Build

    • Compile and Build RPMS

  • Host

    • Copy generated RPM to the component storage path and tag the Build
    • Create RPM Repo to host the RPM'source

  • Integration

    • Trigger the Release job to do the integrated release

  • Notification

    • Type : Jira comments Updates

    • Content:

      • Build info & RPM CI location

    • Type : Mail Notification

    • Content:

      • On Success - Build info & RPM CI location
      • On Failure - Failure Cause

Note

• S3server and Hare components having direct dependency to motr build version so when ever motr build is triggered it requires to rebuild S3server and Hare components.
• S3server, CSM and SSPL component having additional prod pipeline.