Skip to content
Snippets Groups Projects
  1. Nov 01, 2016
  2. Oct 31, 2016
  3. Sep 29, 2016
  4. Sep 28, 2016
  5. Sep 19, 2016
  6. Sep 14, 2016
  7. Aug 19, 2016
  8. Aug 16, 2016
  9. Jul 12, 2016
  10. Jul 11, 2016
  11. Jul 10, 2016
  12. Jul 06, 2016
  13. Jul 03, 2016
  14. Jul 01, 2016
    • Marin Jankovski's avatar
      Merge branch 'bump-chef-zero' into 'master' · 2a85e200
      Marin Jankovski authored and Marin Jankovski's avatar Marin Jankovski committed
      Bump chef-zero to 4.7.0 to retain Ruby 2.1 compatibility
      
      https://github.com/chef/chef-zero/pull/219
      
      The release builds were failing:
      
      ```
                     [Builder: chef-zero] I | gem `install chef-zero --version '4.5.0' --bindir '/opt/gitlab/embedded/bin' --no-ri --no-rdoc': 39.2814s
                     [Builder: chef-zero] I | Build chef-zero: 39.2832s
      The following shell command exited with status 1:
      
          $ CFLAGS=-I/opt/gitlab/embedded/include -O2 CPPFLAGS=-I/opt/gitlab/embedded/include -O2 CXXFLAGS=-I/opt/gitlab/embedded/include -O2 LDFLAGS=-Wl,-rpath,/opt/gitlab/embedded/lib -L/opt/gitlab/embedded/lib LD_RUN_PATH=/opt/gitlab/embedded/lib PATH=/opt/gitlab/bin:/opt/gitlab/embedded/bin:/root/gems/ruby/2.1.0/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin PKG_CONFIG_PATH=/opt/gitlab/embedded/lib/pkgconfig /opt/gitlab/embedded/bin/gem install chef-zero --version '4.5.0' --bindir '/opt/gitlab/embedded/bin' --no-ri --no-rdoc
      
      Output:
      
          (nothing)
      
      Error:
      
          ERROR:  Error installing chef-zero:
      	rack requires Ruby version >= 2.2.2.
      ```
      
      See merge request !852
      2a85e200
  15. Jun 30, 2016
  16. Jun 29, 2016
  17. Jun 28, 2016
  18. Jun 27, 2016
  19. Jun 25, 2016
  20. Jun 23, 2016
  21. Jun 22, 2016
    • Marin Jankovski's avatar
      Merge branch 'feature/pg-slave-detection' into 'master' · 7a844742
      Marin Jankovski authored and Rémy Coutable's avatar Rémy Coutable committed
      
      Prevent running CREATE EXTENSION in a slave server
      
      When you have replication enabled, you can have for a specific space of time your slave node without all database changes from master. The same can happen when you have an issue with replication.
      
      This is not usually a problem to omnibus but as recently we try to enable extensions, we should take extra care that we are not trying to do that on the slave server, as it is running in read-only mode and therefore will fail. It will get this changes from the replication itself, so no harm here.
      
      Fixes gitlab-org/gitlab-ee#628
      
      See merge request !829
      
      Signed-off-by: default avatarRémy Coutable <remy@rymai.me>
      Verified
      7a844742
Loading