Skip to content
Snippets Groups Projects
This project is mirrored from https://:*****@gitlab.com/gitlab-org/omnibus-gitlab.git. Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer or owner.
Last successful update .
  1. Dec 04, 2020
  2. Nov 09, 2020
  3. Jun 24, 2020
    • Ian Baum's avatar
      Upgrade chef and it's related gems to version 15.9.17 · 5e27a55a
      Ian Baum authored and DJ Mountney's avatar DJ Mountney committed
      * Curently on 14, which was set to end of life at on April 30, 2020.
      * Adds chef-bin gem
      * Automatically accept the chef license EULA
      * Update chef libraries in Gemfile to newer versions
      * Update trigger jobs to use ruby 2.6 image
      5e27a55a
  4. Jun 18, 2020
  5. Jun 10, 2020
  6. Jun 02, 2020
  7. May 15, 2020
    • Stan Hu's avatar
      Update CA certificate bundle · 7c7e70a9
      Stan Hu authored
      This hasn't been updated in over a year, and there are a few expired
      certificates in this trust chain.
      7c7e70a9
  8. May 13, 2020
  9. May 12, 2020
  10. Apr 01, 2020
  11. Mar 27, 2020
  12. Mar 18, 2020
  13. Feb 12, 2020
  14. Feb 05, 2020
  15. Jan 31, 2020
  16. Jan 22, 2020
  17. Jan 13, 2020
  18. Dec 30, 2019
  19. Dec 24, 2019
  20. Dec 18, 2019
  21. Oct 21, 2019
  22. Oct 04, 2019
    • Stan Hu's avatar
      Use MD5 checksums in the registry's Google storage driver · dbcff614
      Stan Hu authored
      We saw high number of 500 errors by users accessing the container
      registry (https://gitlab.com/gitlab-org/gitlab/issues/32907) due to
      manifest files showing up as 0-byte files. While it's not clear at the
      moment whether this is a bug in the storage driver or an issue on
      Google's infrastructure, adding a MD5 checksum should ensure Google will
      not write a file that doesn't match the intended value.
      
      Note that this patches both the Google Cloud Storage (GCS) driver and
      the vendored Google Cloud SDK, since the SDK used (circa 2015) is so old
      it doesn't actually have full support for sending MD5 checksums. This
      commit grafted on changes from the latest SDK, which significantly
      changed the interface.
      
      Note that MD5 checksums are only attached to data sent via the PutObject
      interface, which is responsible for writing relatively small payloads
      (e.g. manifest files).
      dbcff614
  23. Jul 12, 2019
  24. Jun 24, 2019
  25. May 13, 2019
  26. May 12, 2019
  27. May 05, 2019
  28. May 02, 2019
  29. Apr 01, 2019
  30. Mar 28, 2019
  31. Mar 26, 2019
  32. Mar 22, 2019
  33. Mar 14, 2019
  34. Mar 13, 2019
Loading