1. 05 Feb, 2019 1 commit
  2. 01 Feb, 2019 3 commits
  3. 30 Jan, 2019 1 commit
  4. 24 Jan, 2019 3 commits
  5. 17 Jan, 2019 1 commit
    • Rémy Coutable's avatar
      [Review Apps] Don't exit when dependable job fails · a4f73241
      Rémy Coutable authored
      The function that retrieves the dependable job is pretty basic and
      retrieves the first job found with the matching name, but this job can
      be failed but then successfully retried. In that case, we would exit the
      depending job even though the dependable job actually succeeded (the
      second time). Let's simplify things, be optimistic and continue with the
      depending job even if the dependable job fails.
      
      That reverts to the original behavior.
      Signed-off-by: Rémy Coutable's avatarRémy Coutable <remy@rymai.me>
      a4f73241
  6. 01 Jan, 2019 1 commit
  7. 31 Dec, 2018 3 commits
  8. 21 Dec, 2018 1 commit
    • Mark Lapierre's avatar
      Exit as error if job fails · 38a10e38
      Mark Lapierre authored
      If a script is waiting for a job to be done and that job fails,
      exit with an error status so that the script doesn't continue
      with a prerequisite in an invalid state.
      38a10e38
  9. 19 Dec, 2018 1 commit
  10. 18 Dec, 2018 1 commit
  11. 17 Dec, 2018 1 commit
  12. 14 Dec, 2018 1 commit
  13. 13 Dec, 2018 2 commits
  14. 06 Dec, 2018 1 commit
  15. 05 Dec, 2018 1 commit
  16. 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
      schedule.
      
      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.
      ee6fb2b1
  17. 29 Nov, 2018 1 commit
  18. 26 Nov, 2018 2 commits
  19. 22 Nov, 2018 1 commit
  20. 15 Nov, 2018 2 commits
  21. 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.
      62bd2aca
  22. 13 Nov, 2018 1 commit
  23. 11 Nov, 2018 1 commit
  24. 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: Rémy Coutable's avatarRémy Coutable <remy@rymai.me>
      f7f42cf3
  25. 06 Nov, 2018 1 commit
  26. 01 Nov, 2018 2 commits
  27. 31 Oct, 2018 2 commits
  28. 23 Oct, 2018 2 commits
    • Ian Baum's avatar
      Add omitted indentation fix · 41994c2a
      Ian Baum authored
      41994c2a
    • 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
      already
      * Adds variables REVIEW_APPS_AWS_SECRET_KEY and
      REVIEW_APPS_AWS_ACCESS_key
      * review-apps-ce uses a different cipher
      58690a63