1. 19 Jul, 2019 1 commit
  2. 18 Jul, 2019 1 commit
    • Steve Azzopardi's avatar
      Add LXD Custom executor example · 7cb27aab
      Steve Azzopardi authored
      This example creates LXD containers for a specific job and runs the
      script inside of that container. After the job is done the container is
      removed. This tries to follow the same life cycle of the Docker executor
      
      reference #4257
      7cb27aab
  3. 16 Jul, 2019 1 commit
  4. 10 Jul, 2019 1 commit
  5. 05 Jul, 2019 2 commits
  6. 04 Jul, 2019 2 commits
  7. 01 Jul, 2019 1 commit
  8. 28 Jun, 2019 1 commit
  9. 27 Jun, 2019 1 commit
  10. 25 Jun, 2019 1 commit
    • Steve Azzopardi's avatar
      Add docs for not supporting LCOW · 5a14535d
      Steve Azzopardi authored
      1. We do not support Linux Containers on Windows (LCOW) since it's an
      experimental feature from Docker.
      1. One of the biggest headaches is volume management since you are
      running on Windows but then have Linux paths so we would require more
      volume parsing.
      1. Supporting Kubernetes Windows nodes might be a better option in the
      long run #4014
      5a14535d
  11. 24 Jun, 2019 1 commit
  12. 03 Jun, 2019 1 commit
    • Steve Azzopardi's avatar
      Fix default cache volume docker-windows register · 840ba005
      Steve Azzopardi authored
      When the user specifies `docker-windows` `/cache` is still used as a default
      value, which is never correct in any cache. The default cache volume for
      `docker-windows` needs to be `c:\\cache`.
      
      With this, there is only one limitation, the detection of `c:\\cache`
      when the user specified volumes on registration. With the following
      specification `c:\\cache:c:\\User\\ContainerAdministrator\\cache` we fail
      to add the `c:\\cache` to be used as a cache directory and the reason
      for this is because a simple string match is being done. For Linux, it's
      easier since we can split the string with `:` but for Windows `:` is
      part of the volume mounting. To properly support this scenario we
      require to expose the volume parser from Docker which is not ideal. A
      note in the documnetation was added about this.
      
      closes #3915
      840ba005
  13. 31 May, 2019 2 commits
  14. 30 May, 2019 1 commit
  15. 29 May, 2019 1 commit
  16. 28 May, 2019 2 commits
  17. 22 May, 2019 1 commit
  18. 20 May, 2019 1 commit
  19. 13 May, 2019 1 commit
  20. 23 Apr, 2019 1 commit
  21. 19 Apr, 2019 1 commit
  22. 17 Apr, 2019 1 commit
  23. 15 Apr, 2019 1 commit
  24. 09 Apr, 2019 1 commit
  25. 03 Apr, 2019 1 commit
    • Steve Azzopardi's avatar
      Add custom clone path for the build · c9bd231f
      Steve Azzopardi authored
      When the user specifies `GIT_CLONE_PATH` environment variable inside of
      the `.gitlab-ci.yml` if the path is valid it is used to clone and build.
      
      `GIT_CLONE_PATH` takes precedence over the configured build dir and
      the default build dir.
      
      Closes #2211
      c9bd231f
  26. 02 Apr, 2019 1 commit
  27. 25 Mar, 2019 1 commit
  28. 18 Mar, 2019 1 commit
  29. 06 Mar, 2019 2 commits
  30. 01 Mar, 2019 1 commit
  31. 26 Feb, 2019 1 commit
  32. 12 Feb, 2019 1 commit
  33. 07 Feb, 2019 1 commit
  34. 24 Jan, 2019 1 commit
  35. 02 Jan, 2019 1 commit