1. 07 Feb, 2019 1 commit
  2. 17 Dec, 2018 2 commits
  3. 12 Dec, 2018 1 commit
  4. 07 Dec, 2018 2 commits
  5. 06 Dec, 2018 1 commit
  6. 05 Dec, 2018 2 commits
  7. 04 Dec, 2018 5 commits
  8. 29 Nov, 2018 1 commit
  9. 26 Nov, 2018 1 commit
  10. 23 Nov, 2018 1 commit
  11. 22 Nov, 2018 2 commits
  12. 20 Nov, 2018 1 commit
    • Robert Speicher's avatar
      Add dedicated runner tags to assets job · 5c3c9059
      Robert Speicher authored
      Ordinarily it would get the `gitlab-org` tag from
      `dedicated-no-docs-pull-cache-job`, but adding the `docker` tag
      overwrites rather than inherits, so this job has been running on the
      underpowered hardware of the shared runners rather than our dedicated
      runners.
      
      We're also adding a `high-cpu` tag, which doesn't currently do anything
      but will be useful for targeting a runner specifically for this job.
      5c3c9059
  13. 16 Nov, 2018 2 commits
  14. 15 Nov, 2018 3 commits
  15. 14 Nov, 2018 5 commits
  16. 13 Nov, 2018 3 commits
  17. 12 Nov, 2018 1 commit
  18. 10 Nov, 2018 1 commit
  19. 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: 's avatarRémy Coutable <remy@rymai.me>
      f7f42cf3
  20. 31 Oct, 2018 1 commit
  21. 30 Oct, 2018 1 commit
  22. 25 Oct, 2018 1 commit
  23. 24 Oct, 2018 1 commit