BigW Consortium Gitlab

  1. 18 Oct, 2016 1 commit
  2. 03 Oct, 2016 2 commits
  3. 30 Sep, 2016 2 commits
  4. 29 Sep, 2016 1 commit
  5. 20 Sep, 2016 2 commits
  6. 19 Sep, 2016 4 commits
  7. 15 Sep, 2016 1 commit
  8. 13 Sep, 2016 2 commits
  9. 07 Sep, 2016 11 commits
  10. 05 Sep, 2016 1 commit
  11. 29 Aug, 2016 2 commits
  12. 24 Aug, 2016 1 commit
  13. 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
  14. 11 Aug, 2016 1 commit
    • Pre-create all builds for Pipeline when a trigger is received · 39203f1a
      Kamil Trzcinski authored
      This change simplifies a Pipeline processing by introducing a special new status: created.
      This status is used for all builds that are created for a pipeline.
      We are then processing next stages and queueing some of the builds (created -> pending) or skipping them (created -> skipped).
      This makes it possible to simplify and solve a few ordering problems with how previously builds were scheduled.
      This also allows us to visualise a full pipeline (with created builds).
      
      This also removes an after_touch used for updating a pipeline state parameters.
      Right now in various places we explicitly call a reload_status! on pipeline to force it to be updated and saved.
  15. 08 Aug, 2016 1 commit
  16. 27 Jul, 2016 1 commit
  17. 20 Jul, 2016 2 commits
  18. 19 Jul, 2016 4 commits