Read about our upcoming Code of Conduct on this issue

  1. 07 Oct, 2016 1 commit
    • Nick Thomas's avatar
      Add markdown cache columns to the database, but don't use them yet · af001f6c6325
      Nick Thomas authored
      This commit adds a number of _html columns and, with the exception of Note,
      starts updating them whenever the content of their partner fields changes.
      
      Note has a collision with the note_html attr_accessor; that will be fixed later
      
      A background worker for clearing these cache columns is also introduced - use
      `rake cache:clear` to set it off. You can clear the database or Redis caches
      separately by running `rake cache:clear:db` or `rake cache:clear:redis`,
      respectively.
      af001f6c6325
  2. 27 Sep, 2016 1 commit
  3. 23 Sep, 2016 1 commit
  4. 21 Sep, 2016 1 commit
  5. 20 Sep, 2016 1 commit
  6. 19 Sep, 2016 1 commit
  7. 16 Sep, 2016 1 commit
  8. 15 Sep, 2016 2 commits
    • Patricio Cano's avatar
      Added group-specific setting for LFS. · 5f2239269f98
      Patricio Cano authored
      Groups can enable/disable LFS, but this setting can be overridden at the project level. Admin only
      5f2239269f98
    • Timothy Andrew's avatar
      Improve performance of the cycle analytics page. · 52e536c75ee6
      Timothy Andrew authored
      1. These changes bring down page load time for 100 issues from more than
         a minute to about 1.5 seconds.
      
      2. This entire commit is composed of these types of performance
         enhancements:
      
           - Cache relevant data in `IssueMetrics` wherever possible.
           - Cache relevant data in `MergeRequestMetrics` wherever possible.
           - Preload metrics
      
      3. Given these improvements, we now only need to make 4 SQL calls:
      
          - Load all issues
          - Load all merge requests
          - Load all metrics for the issues
          - Load all metrics for the merge requests
      
      4. A list of all the data points that are now being pre-calculated:
      
          a. The first time an issue is mentioned in a commit
      
            - In `GitPushService`, find all issues mentioned by the given commit
              using `ReferenceExtractor`. Set the `first_mentioned_in_commit_at`
              flag for each of them.
      
            - There seems to be a (pre-existing) bug here - files (and
              therefore commits) created using the Web CI don't have
              cross-references created, and issues are not closed even when
              the commit title is "Fixes #xx".
      
          b. The first time a merge request is deployed to production
      
            When a `Deployment` is created, find all merge requests that
            were merged in before the deployment, and set the
            `first_deployed_to_production_at` flag for each of them.
      
          c. The start / end time for a merge request pipeline
      
            Hook into the `Pipeline` state machine. When the `status` moves to
            `running`, find the merge requests whose tip commit matches the
            pipeline, and record the `latest_build_started_at` time for each
            of them. When the `status` moves to `success`, record the
            `latest_build_finished_at` time.
      
          d. The merge requests that close an issue
      
            - This was a big cause of the performance problems we were having
              with Cycle Analytics. We need to use `ReferenceExtractor` to make
              this calculation, which is slow when we have to run it on a large
              number of merge requests.
      
            - When a merge request is created, updated, or refreshed, find the
              issues it closes, and create an instance of
              `MergeRequestsClosingIssues`, which acts as a join model between
              merge requests and issues.
      
            - If a `MergeRequestsClosingIssues` instance links a merge request
              and an issue, that issue closes that merge request.
      
      5. The `Queries` module was changed into a class, so we can cache the
         results of `issues` and `merge_requests_closing_issues` across
         various cycle analytics stages.
      
      6. The code added in this commit is untested. Tests will be added in the
         next commit.
      52e536c75ee6
  9. 13 Sep, 2016 2 commits
    • Yorick Peterse's avatar
      Move pushes_since_gc to Redis · 27f7b8eda3a7
      Yorick Peterse authored
      This moves tracking of the pushes since the last Git GC from PostgreSQL
      to Redis. This reduces the number of writes on the "projects" table.
      This in turn reduces the vacuuming overhead.
      
      The lease used for incrementing the counter has been removed. This lease
      was mostly put in place to prevent high database load but this isn't
      needed anymore due to the counter now being stored in Redis.
      
      Fixes gitlab-org/gitlab-ce#22125
      27f7b8eda3a7
    • Kamil Trzcinski's avatar
      Update db/schema.rb · d8e97401ee3a
      Kamil Trzcinski authored
      d8e97401ee3a
  10. 08 Sep, 2016 1 commit
  11. 05 Sep, 2016 3 commits
  12. 02 Sep, 2016 1 commit
  13. 01 Sep, 2016 2 commits
  14. 31 Aug, 2016 2 commits
  15. 30 Aug, 2016 4 commits
  16. 26 Aug, 2016 4 commits
  17. 25 Aug, 2016 1 commit
  18. 23 Aug, 2016 1 commit
  19. 22 Aug, 2016 2 commits
  20. 19 Aug, 2016 2 commits
    • Douwe Maan's avatar
    • Gokmen Goksel's avatar
      Support integration with Koding (online IDE) · de3a3fd08cbb
      Gokmen Goksel authored
      Koding: #index: landing page for Koding integration
      
      If enabled it will provide a link to open remote Koding instance url
      for now we are also providing the sneak preview video for how
      integration works in detail.
      
      Repository: check whether .koding.yml file exists on repository
      
      Projects: landing page: show Run in IDE (Koding) button if repo has stack file
      
      Projects: MR: show Run in IDE Koding button if repo has stack file on active branch
      
      ProjectHelpers: add_koding_stack: stack generator for provided project
      
      With this helper we will auto-generate the required stack template
      for a given project. For the feature we can request this base template
      from the running Koding instance on integration.
      
      Currently this will provide users to create a t2.nano instance on aws
      and it'll automatically configures the instance for basic requirements.
      
      Projects: empty state and landing page provide shortcuts to create stack
      
      projects_helper: use branch on checkout and provide an entry point
      
      This ${var.koding_queryString_branch} will be replaced with the branch
      provided in query string which will allow us to use same stack template
      for different branches of the same repository.
      
      ref: https://github.com/koding/koding/pull/8597/commits/b8c0e43c4c24bf132670aa8a3cfb0d634acfd09b
      
      projects_helper: provide sha info in query string to use existing vms
      
      With this change we'll be able to query existing vms on Koding side
      based on the commit id that they've created.
      
      ref: https://github.com/koding/koding/pull/8597/commits/1d630fadf31963fa6ccd3bed92e526761a30a343
      
      Integration: Docs: Koding documentation added
      
      Disable /koding route if integration is disabled
      
      Use application settings to enable Koding
      
      Projects_helper: better indentation with strip_heredoc usage
      
      Projects_helper: return koding_url as is if there is no project provided
      
      current_settings: set koding_enabled: false by default
      
      Koding_Controller: to render not_found once integration is disabled
      
      Dashboard_specs: update spec for Koding enabled case
      
      Projects_Helper: make repo dynamic
      
      ref: https://github.com/koding/koding/pull/8597/commits/4d615242f45aaea4c4986be84ecc612b0bb1514c
      
      Updated documentation to have right format
      de3a3fd08cbb
  21. 18 Aug, 2016 2 commits
  22. 17 Aug, 2016 4 commits