Read about our upcoming Code of Conduct on this issue

  1. 24 Oct, 2016 1 commit
  2. 20 Oct, 2016 1 commit
  3. 19 Oct, 2016 1 commit
  4. 17 Oct, 2016 2 commits
  5. 14 Oct, 2016 2 commits
  6. 12 Oct, 2016 2 commits
  7. 07 Oct, 2016 1 commit
  8. 06 Oct, 2016 1 commit
  9. 04 Oct, 2016 1 commit
  10. 03 Oct, 2016 2 commits
  11. 20 Sep, 2016 1 commit
    • Timothy Andrew's avatar
      Implement review comments from @yorickpeterse · 57d5f49c9457
      Timothy Andrew authored
      1. Change multiple updates to a single `update_all`
      2. Use cascading deletes
      3. Extract an average function for the database median.
      4. Move database median to `lib/gitlab/database`
      5. Use `delete_all` instead of `destroy_all`
      6. Minor refactoring
  12. 19 Sep, 2016 4 commits
    • Kamil Trzcinski's avatar
      Fix build_updated · 3d1b1ffcbc1f
      Kamil Trzcinski authored
    • Kamil Trzcinski's avatar
      Fix processing of events when build finished. · e57987a09f79
      Kamil Trzcinski authored
      This solves Pipelines in `running` after all stages do finish.
    • Timothy Andrew's avatar
      Test all cycle analytics pre-calculation code. · fbf82d1d74ae
      Timothy Andrew authored
      All the code that pre-calculates metrics for use in the cycle analytics
      - Ci::Pipeline -> build start/finish
      - Ci::Pipeline#merge_requests
      - Issue -> record default metrics after save
      - MergeRequest -> record default metrics after save
      - Deployment -> Update "first_deployed_to_production_at" for MR metrics
      - Git Push -> Update "first commit mention" for issue metrics
      - Merge request create/update/refresh -> Update "merge requests closing issues"
    • James Lopez's avatar
      squashed - Fix DB exceptions raised importing some specific projects. · 0b4323f97d85
      James Lopez authored
      Better import of labels, milestones and protected branches. Updated relevant specs.
      Loose pipeline validation on importing, so it does not fail when there are missing fields, which are not validated at DB level. Also, updated spec with relevant test.
  13. 15 Sep, 2016 1 commit
    • 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
           - 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.
  14. 14 Sep, 2016 1 commit
  15. 13 Sep, 2016 1 commit
  16. 05 Sep, 2016 2 commits
  17. 02 Sep, 2016 1 commit
  18. 29 Aug, 2016 3 commits
  19. 25 Aug, 2016 2 commits
  20. 19 Aug, 2016 2 commits
  21. 18 Aug, 2016 1 commit
  22. 17 Aug, 2016 2 commits
  23. 16 Aug, 2016 1 commit
  24. 15 Aug, 2016 4 commits