## Description The purpose of this epic will be to revive the repo-sync code-base in order to provide a COMPLETE/RELIABLE solution and restore trust in the Open Source community that we are providing a viable methodology to contribute to the BigBang Project. **Background** The original intention with repo-sync was to provide the community with an opportunity to contribute to the BigBang project via [open-source repositories](https://github.com/DoD-Platform-One) that would link directly back to [Repo1](https://repo1.dso.mil/big-bang). The goal is to not only allow the community to obtain an up-to-date version of the bigbang codebase, but to also be able to open issues as well as Merge Requests that can be merged into the codebase. **Current Solution** The current implementation of [repo-sync](https://repo1.dso.mil/big-bang/team/tools/repo-sync) has become derelict and unsupported due to SME's rolling off of the team. The scope of the repo-sync solution has changed many times since its first creation and has therefore led to suspected unused code and bugs. **Known Shortcomings** the repo-sync application continually breaks its syncing of the repositories, comments and issues. It also must be manually deployed, and its repo1 repository is just a placeholder for whatever code was last uploaded to AWS. In addition, there is no working pipeline providing any testing or automation whatsoever. ## Requirements/Scope - [x] Spike to determine scope of what is needed in order to facilitate a complete repo-sync solution - [x] clean code base and remove unused code to reduce bugs - [ ] identify and fix all bugs with current functionality - [x] ensure that repo-sync repo pipeline provides test coverage and deploys the app to aws - [ ] implement a "monitoring" solution that provides visibility as to the status of repo synchronization, in order to be alerted when the repos are out of sync. ## Out of Scope TBD after spike ## Duration TBD after spike ## Team Tools and Automation ## Epic Team Members | | | | --- | --- | | @jfoster | | | @dpritchettrm | epic lead | | @alieberman | | | @mucles | | | @rehank125 | | | @danilo-patrucco | | ## Dependencies No Known Dependencies ## Risks Still not sure this code is worth salvaging, we could spend a lot of sprints pushing this rock uphill, when a complete new solution could be the way to go. ## Acceptance Criteria - [ ] working application that syncs all bigbang repos without error automatically - [ ] application syncs github issues to Repo1 and labels them as community contribution - [ ] application syncs comments bi-directionally on community contribution issues and MRs (WITHOUT ERRORS) - [ ] application syncs github PRs to Repo1 MR and labels them as community contributions - [ ] application automatically resolves github MRs once merged into Repo1 - [ ] repo pipeline functions properly and deploys app automatically rather that manually - [ ] application provides monitoring as to current status of sync ## Related Issues and/or Epics [Transition Repo-Sync Functionality](https://repo1.dso.mil/groups/big-bang/-/epics/340) ## How this epic maps to P1 Vision or roadmap for Big Bang This epic directly maps to a previously completed goal of providing open-source community contributions. Reference [the Big Bang product roadmap](https://p1.dso.mil/product-roadmap?text=&valueStreams=big%20bang&phases=now&phases=next) to understand the product's immediate and near term roadmap goals. ## How does this proposed work benefit the enterprise using Big Bang and/or end user SRE? This epic directly maps to our goal of providing access to a wider customer base and integrating contributions from the community as a whole. ## How does this benefit the internal Big Bang team This epic directly provides a benefit to internal team operations by by providing them with a better, more reliable, experience with Community Contribution Issues and MRs