Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
7308f4ad
Commit
7308f4ad
authored
Oct 27, 2021
by
Shinya Maeda
Committed by
Russell Dickenson
Oct 27, 2021
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Improve the documentation on the merge request tracking on deploy
parent
d88007b9
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
31 additions
and
0 deletions
+31
-0
doc/api/deployments.md
doc/api/deployments.md
+6
-0
doc/ci/environments/index.md
doc/ci/environments/index.md
+25
-0
No files found.
doc/api/deployments.md
View file @
7308f4ad
...
...
@@ -358,6 +358,12 @@ Example response:
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/35739) in GitLab 12.7.
NOTE:
Not all deployments can be associated with merge requests.
Please see
[
Track what merge requests were deployed to an environment
](
../ci/environments/index.md#track-newly-included-merge-requests-per-deployment
)
for more information.
This API retrieves the list of merge requests shipped with a given deployment:
```
plaintext
...
...
doc/ci/environments/index.md
View file @
7308f4ad
...
...
@@ -308,6 +308,31 @@ Note the following:
for these jobs. This ensures that runners can fetch the repository even after a feature branch is
deleted. For more information, see
[
Ref Specs for Runners
](
../pipelines/index.md#ref-specs-for-runners
)
.
## Track newly included merge requests per deployment
GitLab can track newly included merge requests per deployment.
When a deployment succeeded, the system calculates commit-diffs between the latest deployment and the previous deployment.
This tracking information can be fetched via the
[
Deployment API
](
../../api/deployments.md#list-of-merge-requests-associated-with-a-deployment
)
and displayed at a post-merge pipeline in
[
merge request pages
](
../../user/project/merge_requests/index.md
)
.
To activate this tracking, your environment must be configured in the following:
-
[
Environment name
](
../yaml/index.md#environmentname
)
is not foldered with
`/`
(that is, top-level/long-lived environments), _OR_
-
[
Environment tier
](
#deployment-tier-of-environments
)
is either
`production`
or
`staging`
.
Here are the example setups of
[
`environment` keyword
](
../yaml/index.md#environment
)
in
`.gitlab-ci.yml`
:
```
yaml
# Trackable
environment
:
production
environment
:
production/aws
environment
:
development
# Non Trackable
environment
:
review/$CI_COMMIT_REF_SLUG
environment
:
testing/aws
```
## Working with environments
Once environments are configured, GitLab provides many features for working with them,
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment