summaryrefslogtreecommitdiff
path: root/doc/raketasks
diff options
context:
space:
mode:
authorYorick Peterse <yorickpeterse@gmail.com>2016-07-18 14:11:36 +0200
committerYorick Peterse <yorickpeterse@gmail.com>2016-07-19 13:21:09 +0200
commit499cdf1d19343c985b5a0f21f2333a1b45900b13 (patch)
tree1326ee22c5dd49d8c77398c18de95668fe1aeabc /doc/raketasks
parent240a4aa62ab24a8a7b5545dee6bd2cf00ad7596e (diff)
downloadgitlab-ce-499cdf1d19343c985b5a0f21f2333a1b45900b13.tar.gz
Added Rake task for tracking deploymentsdeployment-tracking
This simply inserts the current GitLab version in the "deployments" measurement. Fixes gitlab-com/infrastructure#98
Diffstat (limited to 'doc/raketasks')
-rw-r--r--doc/raketasks/maintenance.md19
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
+```