Request deployment target info from users on new projects
Goal
As we prepare ourselves for the Deployment Management work, we should constantly aim at better understanding our users including their deployment requirements.
This Sisense query shows how many projects are created per day containing a Dockerfile a few days later. 2-3 days after a project is started, there are often 1000+ projects that already have a Dockerfile. As this was a surprising insight, we would like to get a better understanding of the deployment targets.
We would like to know what is the deployment target on these projects
Proposal
- Ask the user about their deployment target on the new project creation page
- Store the response so we won't ask it again
Add options here
Question: Where do you plan to deploy this project?
Options (multiple choice):
- Kubernetes (GKE, EKS, OpenShift, etc)
- Managed container runtime (Fargate, Cloud Run, Digitalocean App)
- Self-managed container runtime (Podman, Docker Swarm, docker-compose)
- Heroku
- Virtual machine (EC2, etc)
- Mobile app store
- Registry (package or container)
- Infrastructure provider (Terraform, Cloudformation, etc projects)
- Serverless backend (Lambda, Cloud functions)
- GitLab pages
- Other hosting service
- No deployment planned
Iterations
- Could we start with a frontend-only solution on the new project creation page?
- Store it in the DB and collect data from self-managed too
- Show a banner on projects where the value not set
Definition of done
-
Add a multi select to project creation form -
Hook it up to sisense -
Store the value in the DB -
Update usage ping to support this -
Document why we are doing this
Edited by Anna Vovchenko