1. 06 Dec, 2018 1 commit
  2. 05 Dec, 2018 1 commit
  3. 04 Dec, 2018 1 commit
    • Yorick Peterse's avatar
      Automatically merge CE master into EE master · ee6fb2b1
      Yorick Peterse authored
      This sets up GitLab CI to automatically push CE master changes into EE
      master, or revert them if the changes cause merge conflicts. The CI
      configuration contains a single job to do this: `merge:master`. This job
      is executed for every push to master, and periodically using a CI
      The periodic job is necessary because incremental jobs may not be able
      to revert commits if newly added commits depend on these commits. By
      re-running the job periodically (including all changes since a large
      enough time frame), we can ensure that such commits are also reverted
      (if they still conflict at that time).
      The job runs in its own "merge" stage, _after_ the build and prepare
      stages, but _before_ running the tests. This ensures that randomly
      failing tests won't prevent code from being merged into EE. Running the
      stage after the "prepare" stage reduces the chances of the job reverting
      CE changes just because it ran before a corresponding EE MR was merged
      into EE master.
  4. 29 Nov, 2018 1 commit
  5. 26 Nov, 2018 2 commits
  6. 22 Nov, 2018 1 commit
  7. 15 Nov, 2018 2 commits
  8. 14 Nov, 2018 1 commit
    • Jan Provaznik's avatar
      Switch rails 4 to 5 in gitlab-ci · 62bd2aca
      Jan Provaznik authored
      CI jobs will be triggered both with rails 4 and 5
      to make sure we keep backward compatibility if it turns out
      we have to switch back to rails 4.
      Rails 4 jobs are not allowed to fail for now, these jobs will be
      removed in a follow-up MR next cycle.
  9. 13 Nov, 2018 1 commit
  10. 11 Nov, 2018 1 commit
  11. 09 Nov, 2018 1 commit
    • Rémy Coutable's avatar
      Ensure we create the secrets at the right time · f7f42cf3
      Rémy Coutable authored
      In `deploy`, if the previous deployment failed, we delete/cleanup all
      the objects related to the release, including secrets. The problem is
      that if we create the root password before that, it will be then
      recreated during the deploy with a random value!
      By creatigng the secret just before actually deplying a new release, we
      ensure that it won't be overriden.
      Signed-off-by: default avatarRémy Coutable <remy@rymai.me>
  12. 06 Nov, 2018 1 commit
  13. 01 Nov, 2018 2 commits
  14. 31 Oct, 2018 2 commits
  15. 23 Oct, 2018 2 commits
    • Ian Baum's avatar
      Add omitted indentation fix · 41994c2a
      Ian Baum authored
    • Ian Baum's avatar
      Add review app to gitlab-ce · 58690a63
      Ian Baum authored
      * Uses the same supporting code as used in EE
      * Includes automated cleanup
      * Install external-dns helm chart to review apps cluster if it isn't
      * Adds variables REVIEW_APPS_AWS_SECRET_KEY and
      * review-apps-ce uses a different cipher
  16. 22 Oct, 2018 2 commits
  17. 10 Oct, 2018 2 commits
    • Rémy Coutable's avatar
      Improve the variables passed in trigger-build · 4d7c6a61
      Rémy Coutable authored
      Make the variable names consistent by following the
      `TOP_UPSTREAM_SOURCE_*` pattern.
      Signed-off-by: default avatarRémy Coutable <remy@rymai.me>
    • Rémy Coutable's avatar
      Pass 'TOP_UPSTREAM_SOURCE_SHA' in trigger-build · 02b456db
      Rémy Coutable authored
      This is needed because `GITLAB_VERSION` has a special meaning in
      `omnibus-gitlab` triggers: this is the GitLab version to build.
      The problem is that `omnibus-gitlab` also has triggers to run QA for an
      `omnibus-gitlab` commit, and if we use `GITLAB_VERSION` in that case,
      the comment would be posted on the GitLab CE/EE commit (stored in
      `GITLAB_VERSION`), whci hwouldn't make any sense.
      Thus we need `TOP_UPSTREAM_SOURCE_SHA` to represent the commit on
      which we want to leave a comment.
      Signed-off-by: default avatarRémy Coutable <remy@rymai.me>
  18. 08 Oct, 2018 1 commit
  19. 02 Oct, 2018 1 commit
    • Alejandro Rodríguez's avatar
      Remove Gitlab::Git::Repository#rugged and Gollum code · a99bf447
      Alejandro Rodríguez authored
      Cleanup code, and refactor tests that still use Rugged. After this, there should
      be no Rugged code that access the instance's repositories on non-test
      environments. There is still some rugged code for other tasks like the
      repository import task, but since it doesn't access any repository storage path
      it can stay.
  20. 01 Oct, 2018 1 commit
  21. 25 Sep, 2018 1 commit
  22. 24 Sep, 2018 1 commit
  23. 30 Aug, 2018 1 commit
  24. 29 Aug, 2018 1 commit
  25. 19 Aug, 2018 1 commit
  26. 16 Aug, 2018 1 commit
  27. 19 Jul, 2018 1 commit
  28. 09 Jul, 2018 1 commit
  29. 05 Jul, 2018 1 commit
  30. 25 Jun, 2018 2 commits
  31. 20 Jun, 2018 1 commit
  32. 15 Jun, 2018 1 commit