Discovery and cataloging of existing edxapp pipeline

[robrap]

• Document the various edxapp pipelines, stages and jobs in GoCD.
• Determine which would need to remain as-is, or partially, in GoCD.
  • For example, if build_edxapp_amis:prerelease_materials handles the sync with edx-platform-private, that will need to live on.
• Is investigation into the configuration repo or tubular code needed for this discovery?
• We need a rollout plan for transitioning the pipeline.
  • Will we be slowly transforming the existing pipeline to introduce ArgoCD, or will we be introducing a brand new pipeline?
  • How do we deal with migrating processes that should only happen once (e.g. migrations, edx-platform-private sync, etc.)?
  • If we have a containerized stage environment, would we want e2e tests to ever run against this temporary environment?
  • Other questions regarding transitioning the pipeline?
• Can we document requirements to maintain parity with our current pipeline?
  • For example, we want to maintain the ability to auto-deploy to Production.

UPDATE: It seems like SRE is planning on taking on this work, and creating a new GoCD pipeline. I think it will still be useful to help with the inventory, requirements definition, and ensuring that all of the proper SRE ticketing happens.

• Possibly as part of this ticket, or a separate ticket, we should catalog all the dependencies (e.g. database, memcached, elasticsearch, braze, etc.). This would probably come from review of the settings. This wil also affect the ultimate test plan.
• May want to create another ticket with a checklist of items we are expecting SRE to implement, so that we can be clear on the list and validating that the work is completed. It might point to SRE tickets as-needed as well.