Uploaded image for project: 'Drivers'
  1. Drivers
  2. DRIVERS-1383

Automate Driver Releases

    • Type: Icon: Epic Epic
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Component/s: None
    • None
    • To Do
    • Automate Driver Releases
    • 100
    • Needed

      Epic Summary

      Outline a roadmap to move all drivers to evergreen-based-releases.

      Drivers releases are often downloaded from package index (pip, maven, cpan) or from github directly. Currently only some of the driver releases are signed and the process of signing them is not standardized. Releasing drivers via Evergreen will allow us to better audit the release process (including signing packages). For many of our customers there is a requirement to adhere to an SDLC process that ensures the packages we provide are not tampered with by any internal participant in the process of producing and releasing those packages. Often these requirements are stated by our customers in security and compliance questionnaires. Currently, we list exceptions on these questionnaires related to drivers SDLC and signed packages. This effort should reduce the friction during sales cycles due to the number of exceptions we list.

      Cast of Characters

      Document Author: Rathi Gnanasekaran
      Product Owner: Rachelle Palmer
      Program Manager: Alexander Golin & Esha Bhargava
      Stakeholders: Drivers


      Scope Document
      Evergreen Documentation

            Unassigned Unassigned
            alexander.golin@mongodb.com Alexander Golin (Inactive)
            0 Vote for this issue
            0 Start watching this issue