Skip to content
Snippets Groups Projects
  1. Jun 14, 2022
  2. May 29, 2022
  3. May 24, 2022
  4. May 20, 2022
  5. May 11, 2022
  6. Apr 29, 2022
  7. Apr 26, 2022
  8. Apr 25, 2022
  9. Apr 13, 2022
    • Harsh Chouraria's avatar
      Remove 1-node zero downtime instructions · 22c17b6c
      Harsh Chouraria authored and Achilleas Pipinellis's avatar Achilleas Pipinellis committed
      With only Puma carried in GitLab 14.0 onwards
      there is no possibility of minimizing any downtime
      in single-node upgrades.
      
      When the migration is run while leaving
      the previous version's puma running, the
      database changes are picked up in Rails
      dynamically and UI errors begin to be
      thrown to users.
      
      Given the disruption of features is essentially
      the same to users as a downtime when it
      affects critical features such as merge requests
      the section is false in indicating that
      downtime is minimized.
      
      Additionally this section is often discovered
      by users and blindly followed even for
      multiple version jumps that leads to
      broken upgrades.
      
      This change removes all sections related to zero
      downtime upgrade instructions of single nodes.
      22c17b6c
  10. Apr 07, 2022
  11. Mar 30, 2022
  12. Mar 24, 2022
  13. Feb 22, 2022
  14. Feb 14, 2022
  15. Jan 28, 2022
  16. Jan 26, 2022
  17. Jan 12, 2022
  18. Dec 28, 2021
  19. Dec 17, 2021
  20. Dec 15, 2021
  21. Sep 15, 2021
  22. Aug 18, 2021
  23. Jul 22, 2021
  24. Jul 15, 2021
  25. Jul 08, 2021
  26. Jun 29, 2021
  27. Jun 23, 2021
  28. Jun 11, 2021
  29. Mar 17, 2021
  30. Feb 26, 2021
  31. Feb 12, 2021
  32. Feb 11, 2021
  33. Jan 29, 2021
  34. Jan 28, 2021
  35. Jan 12, 2021
  36. Dec 24, 2020
Loading