From 499cdf1d19343c985b5a0f21f2333a1b45900b13 Mon Sep 17 00:00:00 2001 From: Yorick Peterse Date: Mon, 18 Jul 2016 14:11:36 +0200 Subject: Added Rake task for tracking deployments This simply inserts the current GitLab version in the "deployments" measurement. Fixes gitlab-com/infrastructure#98 --- doc/raketasks/maintenance.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) (limited to 'doc/raketasks') 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 +``` -- cgit v1.2.1