diff options
| author | Rémy Coutable <remy@rymai.me> | 2016-07-19 12:33:45 +0000 |
|---|---|---|
| committer | Rémy Coutable <remy@rymai.me> | 2016-07-19 16:34:54 +0200 |
| commit | e8acbac3f2d339be404eb6c944a9aaf2154cf52a (patch) | |
| tree | e78b9f3330781a4e7de411fd62c7078a07fe0a10 /doc | |
| parent | e9e750f594bbc4d5cd816988de8fe992598cc186 (diff) | |
| download | gitlab-ce-e8acbac3f2d339be404eb6c944a9aaf2154cf52a.tar.gz | |
Merge branch 'deployment-tracking' into 'master'
Added Rake task for tracking deployments
## What does this MR do?
This MR adds a Rake task to track the current version of GitLab in InfluxDB.
## Are there points in the code the reviewer needs to double check?
We may want to document this Rake task in some Markdown file, but I'm not sure what the best place for this would be.
## Why was this MR needed?
We want to have a more accurate overview of when deployments occurred.
## What are the relevant issue numbers?
https://gitlab.com/gitlab-com/infrastructure/issues/98
## Does this MR meet the acceptance criteria?
- [x] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added
- [x] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)
- [x] ~~API support added~~
- [x] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides)
- [ ] Branch has no merge conflicts with `master` (if you do - rebase it please)
- [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
See merge request !5320
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/raketasks/maintenance.md | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/doc/raketasks/maintenance.md b/doc/raketasks/maintenance.md index d9dce2af480..315cb56a089 100644 --- a/doc/raketasks/maintenance.md +++ b/doc/raketasks/maintenance.md @@ -167,3 +167,22 @@ of those assets. Unless you are modifying the JavaScript / CSS code on your production machine after installing the package, there should be no reason to redo rake assets:precompile on the production machine. If you suspect that assets have been corrupted, you should reinstall the omnibus package. + +## Tracking Deployments + +GitLab provides a Rake task that lets you track deployments in GitLab +Performance Monitoring. This Rake task simply stores the current GitLab version +in the GitLab Performance Monitoring database. + +For Omnibus-packages: + +``` +sudo gitlab-rake gitlab:track_deployment +``` + +For installations from source: + +``` +cd /home/git/gitlab +sudo -u git -H bundle exec rake gitlab:track_deployment RAILS_ENV=production +``` |