Read about our upcoming Code of Conduct on this issue

  1. 07 Jan, 2019 1 commit
  2. 04 Jan, 2019 2 commits
    • Kamil Trzciński's avatar
      Add config_options|variables to BuildMetadata · 2ec8bcf6063b
      Kamil Trzciński authored
      These are data columns that store runtime configuration
      of build needed to execute it on runner and within pipeline.
      
      The definition of this data is that once used, and when no longer
      needed (due to retry capability) they can be freely removed.
      
      They use `jsonb` on PostgreSQL, and `text` on MySQL (due to lacking
      support for json datatype on old enough version).
      2ec8bcf6063b
    • Shinya Maeda's avatar
      Support CURD operation for release asset links · 7b2ba8f93c91
      Shinya Maeda authored
      - Add Releases::Links model
      - Expose it in release API
      - Add integration tests
      7b2ba8f93c91
  3. 05 Dec, 2018 1 commit
  4. 20 Nov, 2018 2 commits
  5. 17 Nov, 2018 1 commit
    • gfyoung's avatar
      Enable even more frozen string for lib/gitlab · d5b60d4845e5
      gfyoung authored
      Enables frozen string for the following:
      
      * lib/gitlab/hook_data/**/*.rb
      * lib/gitlab/i18n/**/*.rb
      * lib/gitlab/import/**/*.rb
      * lib/gitlab/import_export/**/*.rb
      * lib/gitlab/kubernetes/**/*.rb
      * lib/gitlab/legacy_github_import/**/*.rb
      * lib/gitlab/manifest_import/**/*.rb
      * lib/gitlab/metrics/**/*.rb
      * lib/gitlab/middleware/**/*.rb
      
      Partially addresses gitlab-org/gitlab-ce#47424.
      d5b60d4845e5
  6. 24 Sep, 2018 1 commit
  7. 10 Aug, 2018 1 commit
  8. 27 Jun, 2018 1 commit
  9. 25 Jun, 2018 1 commit
  10. 22 Jun, 2018 2 commits
  11. 20 Jun, 2018 3 commits
  12. 19 Jun, 2018 2 commits
  13. 30 May, 2018 1 commit
  14. 15 May, 2018 1 commit
    • Stan Hu's avatar
      Add a unique and not null constraint on the project_features.project_id column · 240f12998a18
      Stan Hu authored
      This commit has two migrations:
      
      1. The first prunes duplicate rows in the project_features table and leaves
         the row with the highest ID.  Since the behavior was indeterministic before
         and depended on which row the database decided to use, this change at least
         makes the permissions consistent. For example, in some cases, the Wiki may
         have been disabled but enabled in another entry.
      
      2. The second adds a non-null constraint on the project_features.project_id
         column.
      
      Closes #37882
      
      Fixes a significant part of gitlab-com/migration#408.
      
      We found that we were overcounting Wikis because of these duplicates.
      On GitLab.com, there are 56 rows with duplicate entries by project_id, and 16,661 rows with NULL project_id values.
      240f12998a18
  15. 14 May, 2018 1 commit
  16. 16 Apr, 2018 1 commit
    • Yorick Peterse's avatar
      Introduce new ProjectCiCdSetting · 748b19fa2048
      Yorick Peterse authored
      This model and the corresponding table will be used for storing settings
      specific to CI/CD, starting with the "group_runners_enabled" boolean.
      
      The model is called ProjectCiCdSetting and not ProjectCiCdSettings. The
      project exporter doesn't like plural model names as it uses "classify"
      which turns those into singular (so "ProjectCiCdSettings" becomes
      "ProjectCiCdSetting", producing an error if said class is undefined).
      
      The initial work in this commit was done by Dylan Griffith, with most of
      the migration work being done by Yorick Peterse.
      748b19fa2048
  17. 14 Mar, 2018 1 commit
    • Bob Van Landuyt's avatar
      Import multiple issue assignees from GitLab export · aaa9af63c0b3
      Bob Van Landuyt authored
      When importing from a GitLab archive, an admin can carry over the
      assignations. Other users can not.
      
      When a regular user is importing an issue with multiple assignees, the
      assignee is replaced with the current user, meaning we would try to
      insert current user as an assignee multiple times.
      
      By filtering the array before storing it, the import becomes more
      robust.
      aaa9af63c0b3
  18. 05 Mar, 2018 1 commit
  19. 01 Mar, 2018 1 commit
  20. 02 Feb, 2018 1 commit
  21. 11 Jan, 2018 1 commit
  22. 05 Jan, 2018 1 commit
  23. 28 Nov, 2017 1 commit
    • Sean McGivern's avatar
      Remove serialised diff and commit columns · 701b9ccc8a4b
      Sean McGivern authored
      The st_commits and st_diffs columns on merge_request_diffs historically held the
      YAML-serialised data for a merge request diff, in a variety of formats.
      
      Since 9.5, these have been migrated in the background to two new tables:
      merge_request_diff_commits and merge_request_diff_files. That has the advantage
      that we can actually query the data (for instance, to find out how many commits
      we've stored), and that it can't be in a variety of formats, but must match the
      new schema.
      
      This is the final step of that journey, where we drop those columns and remove
      all references to them. This is a breaking change to the importer, because we
      can no longer import diffs created in the old format, and we cannot guarantee
      the export will be in the new format unless it was generated after this commit.
      701b9ccc8a4b
  24. 07 Nov, 2017 1 commit
  25. 06 Nov, 2017 2 commits
  26. 01 Nov, 2017 1 commit
  27. 06 Oct, 2017 1 commit
  28. 05 Oct, 2017 1 commit
  29. 04 Oct, 2017 2 commits
  30. 06 Sep, 2017 1 commit
    • Yorick Peterse's avatar
      Finish migration to the new events setup · 6f43f86cfef6
      Yorick Peterse authored
      This finishes the procedure for migrating events from the old format
      into the new format. Code no longer uses the old setup and the database
      tables used during the migration process are swapped, with the old table
      being dropped.
      
      While the database migration can be reversed this will 1) take a lot of
      time as data has to be coped around 2) won't restore data in the
      "events.data" column as we have no way of restoring this.
      
      Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/37241
      6f43f86cfef6
  31. 04 Sep, 2017 2 commits