Build GitLab feature to create sample data for demo and testing purposes
Context from the PM/Eng meeting agenda: https://docs.google.com/document/d/1D9rW65d4w0UwSRw_0jJMRk5wAxdhAd4ynrHLbMMwIjo/edit#bookmark=id.qe6uy3xa0d83
Requirements
- Help customer success go faster but also offer it to anyone.
- Demo env needs helpful content (pre-populated data). Need sample project as GitLab feature.
- Make it super easy/push-button. Populate project with data.
- Driven by Quality data/scripts or import/export behind the scenes.
Duplication of data
Moved to track in #10363 (moved)
Plan
-
Review demo projects under the sales/demo project -
Review demo projects under test from quality starting with performance test. -
Work on unblocking the mechanisms to provide a better data structure. -
import repository/code and do not include any other features (ex. issues, milestones, CI/CD, etc.)
-
Fix: We need to ensure the import and export mechanism support issues, milestones, runner and CI configuration.
-
-
missing group import/export capabilities that include group-level features and the nested projects in that group.
-
We need to ensure that the import/export capabilities can handle sub group structure.
-
-
static date stamps that will become stale
-
We need to enhance the API where when we create the project there is a flag to refresh the dates and take the present date when we create the demo project.
-
-
-
Work on storing demo project data inside the product that can be shipped with GitLab. - This can be stored statically as
yaml
and when we create the project we can rev up the dates.
- This can be stored statically as
-
Work on mechanism to create the project, this needs to be a GitLab feature facing mechanism. - We can start with an MVP page that has a simple UI that takes in the location of the project and a button to start the creation.
Edited by Mek Stittri