1. 15 Nov, 2018 3 commits
  2. 14 Nov, 2018 4 commits
  3. 13 Nov, 2018 3 commits
  4. 12 Nov, 2018 1 commit
  5. 10 Nov, 2018 1 commit
  6. 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>
      f7f42cf3
  7. 31 Oct, 2018 1 commit
  8. 30 Oct, 2018 1 commit
  9. 25 Oct, 2018 1 commit
  10. 24 Oct, 2018 2 commits
  11. 23 Oct, 2018 4 commits
  12. 22 Oct, 2018 1 commit
  13. 04 Oct, 2018 1 commit
  14. 02 Oct, 2018 1 commit
  15. 01 Oct, 2018 1 commit
  16. 29 Sep, 2018 1 commit
  17. 28 Sep, 2018 1 commit
  18. 25 Sep, 2018 1 commit
  19. 24 Sep, 2018 1 commit
  20. 19 Sep, 2018 1 commit
    • DJ Mountney's avatar
      Move the cloud-native-image trigger job into the test stage · 19d84a60
      DJ Mountney authored
      This is because the CNG pipeline now relies on the assets
      compiled here in the gitlab:assets:compile job (It waits
      up to 30 minutes for them)
      
      Without this change, the cloud native job was holding up
      the pipeline, preventing the assets compile job from being
      run.
      19d84a60
  21. 11 Sep, 2018 1 commit
  22. 07 Sep, 2018 2 commits
  23. 03 Sep, 2018 1 commit
  24. 02 Sep, 2018 1 commit
  25. 28 Aug, 2018 1 commit
    • Sean McGivern's avatar
      Move package-and-qa to the test phase · 4f3a2347
      Sean McGivern authored
      The problem is this: when each phase starts, it checks if all jobs in earlier
      phases are complete. package-and-qa is slow. As build is the first phase, if you
      trigger package-and-qa before the prepare phase is finished, the entire test
      phase will be blocked until package-and-qa completes, which isn't what we want.
      
      But equally, if build came _after_ test, then package-and-qa couldn't be started
      until the tests were finished. Putting it in the same stage as the tests means
      we can have our cake and eat it.
      4f3a2347
  26. 17 Aug, 2018 1 commit
  27. 09 Aug, 2018 1 commit
    • Bob Van Landuyt's avatar
      Disable danger in preparation branches · 1ea6d585
      Bob Van Landuyt authored
      Most of these validations don't apply to preparation branches and they
      cause a lot of noise in the merge request. Therefore disabling danger
      when the branches look like branches that could be for a preparation MR.
      1ea6d585
  28. 26 Jul, 2018 1 commit