BigW Consortium Gitlab

  1. 24 Aug, 2016 1 commit
  2. 17 Aug, 2016 1 commit
    • Tracking of custom events · d345591f
      Yorick Peterse authored
      GitLab Performance Monitoring is now able to track custom events not
      directly related to application performance. These events include the
      number of tags pushed, repositories created, builds registered, etc.
      
      The use of these events is to get a better overview of how a GitLab
      instance is used and how that may affect performance. For example, a
      large number of Git pushes may have a negative impact on the underlying
      storage engine.
      
      Events are stored in the "events" measurement and are not prefixed with
      "rails_" or "sidekiq_", this makes it easier to query events with the
      same name triggered from different parts of the application. All events
      being stored in the same measurement also makes it easier to downsample
      data.
      
      Currently the following events are tracked:
      
      * Creating repositories
      * Removing repositories
      * Changing the default branch of a repository
      * Pushing a new tag
      * Removing an existing tag
      * Pushing a commit (along with the branch being pushed to)
      * Pushing a new branch
      * Removing an existing branch
      * Importing a repository (along with the URL we're importing)
      * Forking a repository (along with the source/target path)
      * CI builds registered (and when no build could be found)
      * CI builds being updated
      * Rails and Sidekiq exceptions
      
      Fixes gitlab-org/gitlab-ce#13720
  3. 03 Jun, 2016 4 commits
  4. 19 May, 2016 1 commit
  5. 23 Feb, 2016 1 commit
  6. 17 Feb, 2016 1 commit
  7. 26 Jan, 2016 1 commit
  8. 20 Nov, 2015 1 commit
  9. 18 Nov, 2015 2 commits
  10. 09 Sep, 2015 1 commit
  11. 23 Aug, 2015 1 commit
    • Remove user OAuth tokens stored in database for Bitbucket, GitHub, and GitLab · ed1d4fa4
      Stan Hu authored
      and request them each session. Pass these tokens to the project import data.
      
      This prevents the need to encrypt these tokens and clear them in case they
      expire or get revoked.
      
      For example, if you deleted and re-created OAuth2 keys for Bitbucket, you would get
      an Error 500 with no way to recover:
      
      ```
      Started GET "/import/bitbucket/status" for x.x.x.x at 2015-08-07 05:24:10 +0000
      Processing by Import::BitbucketController#status as HTML
      Completed 500 Internal Server Error in 607ms (ActiveRecord: 2.3ms)
      
      NameError (uninitialized constant Import::BitbucketController::Unauthorized):
        app/controllers/import/bitbucket_controller.rb:77:in `rescue in go_to_bitbucket_for_permissions'
        app/controllers/import/bitbucket_controller.rb:74:in `go_to_bitbucket_for_permissions'
        app/controllers/import/bitbucket_controller.rb:86:in `bitbucket_unauthorized'
      ```
      
      Closes #1871
  12. 11 Aug, 2015 2 commits
  13. 17 Jul, 2015 1 commit
  14. 15 Jul, 2015 1 commit
  15. 03 Apr, 2015 1 commit
  16. 24 Feb, 2015 2 commits
  17. 06 Feb, 2015 1 commit
  18. 05 Feb, 2015 2 commits
  19. 10 Jan, 2015 1 commit
  20. 03 Oct, 2014 1 commit
  21. 11 Jun, 2014 1 commit
  22. 12 Mar, 2014 2 commits
  23. 08 Nov, 2013 1 commit
  24. 12 Aug, 2013 1 commit