Deployment Detail Page (or Deployment Request similar to Merge Request)
Release notes
Problem to solve
Today, users don't have a place to examine and discuss a specific deployment. For example,
- Fundamental information:
- Users want to know what new commits included in the deployment. (Reference)
- Users want to know what new merge requests are included in the deployment.
- Users want to know who's the DRI of the deployment execution.
- Users want to know the due date of the deployment.
- Users want to know the milestone of the deployment.
- Users want to know the pipeline status of the deployment job.
- Users want to know which release is associated to the deployment.
- Users want to know the deployment ID (global ID) along side the Deployment IID (project internal ID) for API usage.
- Users want to know the other environment's status having the same deployment commit e.g. Check the staging environment health before promoting the deployment to production environment. (Horizontal deployment)
- For the upcoming deployment (manually executable):
- Users want to review the deployment based on the fundamental information and approve/reject it after the review completion.
- Users want to start discussions on the specific deployment e.g. QA team asks a question to a development team if the included code change won't be disruptive.
- Users want to see who has already approved, who has permission to approve and how many approvals are missing. Related.
- Users want to see who is allowed to deploy i.e. protected environment details. related
- Users want to execute the deployment from the page - either clicking a button or quick actions.
- Users want to know what CI variables will be used when the deployment job is executed.
- For the finished deployment:
- Users want to know the timeline of the events.
- The system notifies the user if an invalid environment not being updated.
- Users want to know what CI variables was used at execution.
These are very fundamental information to operate a specific deployment, which is crucial piece to improve the maturity of our Environments and deployments feature.
For the next iteration, we'll make the detail page to be issuable in order to provide a place to discuss the deployments.
Intended users
User experience goal
Proposal
We add Deployment Detail page.
- The page displays the fundamental information by default.
- Users can start discussions by making it to Issue-style.
- The issue state will be open at first. When the deployment finished, it's automatically closed.
Further details
Today, we only have the following pages:
Permissions and Security
There is no permission change from the current Deployment read/write models.
-
Add expected impact to members with no access (0) -
Add expected impact to Guest (10) members -
Add expected impact to Reporter (20) members -
Add expected impact to Developer (30) members -
Add expected impact to Maintainer (40) members -
Add expected impact to Owner (50) members
Documentation
Availability & Testing
Available Tier
- Free
Feature Usage Metrics
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
What is the competitive advantage or differentiation for this feature?
Links / references
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.