1. 02 Apr, 2020 1 commit
  2. 18 Mar, 2020 1 commit
  3. 13 Mar, 2020 1 commit
  4. 15 Feb, 2020 1 commit
  5. 15 Jan, 2020 1 commit
  6. 10 Jan, 2020 1 commit
  7. 05 Dec, 2019 1 commit
  8. 28 Nov, 2019 1 commit
  9. 19 Nov, 2019 1 commit
  10. 08 Nov, 2019 2 commits
  11. 24 Oct, 2019 1 commit
  12. 16 Oct, 2019 1 commit
  13. 13 Sep, 2019 1 commit
  14. 30 Aug, 2019 1 commit
  15. 01 Aug, 2019 1 commit
  16. 29 Jul, 2019 1 commit
  17. 17 Jun, 2019 1 commit
    • Yorick Peterse's avatar
      Backport the EE schema and migrations to CE · 6c7a2f164755
      Yorick Peterse authored
      This backports all EE schema changes to CE, including EE migrations,
      ensuring both use the same schema.
      
      == Updated tests
      
      A spec related to ghost and support bot users had to be modified to make
      it pass. The spec in question assumes that the "support_bot" column
      exists when defining the spec. In the single codebase setup this is not
      the case, as the column is backported in a later migration. Any attempt
      to use a different schema version or use of "around" blocks to
      conditionally disable specs won't help, as reverting the backport
      migration would also drop the "support_bot" column. Removing the
      "support_bot" tests entirely appears to be the only solution.
      
      We also need to update some foreign key tests now that we have
      backported the EE columns. Fortunately, these changes are very minor.
      
      == Backporting migrations
      
      This commit moves EE specific migrations (except those for the Geo
      tracking database) and related files to CE, and also removes any traces
      of the ee/db directory.
      
      Some migrations had to be modified or removed, as they no longer work
      with the schema being backported. These migrations were all quite old,
      so we opted for removing them where modifying them would take too much
      time and effort.
      
      Some old migrations were modified in EE, while also existing in CE. In
      these cases we took the EE code, and in one case removed them entirely.
      It's not worth spending time trying to merge these changes somehow as we
      plan to remove old migrations around the release of 12.0, see
      https://gitlab.com/gitlab-org/gitlab-ce/issues/59177 for more details.
      6c7a2f164755
  18. 13 Jun, 2019 1 commit
  19. 15 Feb, 2019 1 commit
  20. 07 Jan, 2019 1 commit
  21. 13 Dec, 2018 1 commit
  22. 15 Nov, 2018 2 commits