1. 01 Nov, 2016 1 commit
  2. 31 Oct, 2016 5 commits
  3. 29 Sep, 2016 1 commit
  4. 28 Sep, 2016 1 commit
  5. 19 Sep, 2016 2 commits
  6. 14 Sep, 2016 3 commits
  7. 19 Aug, 2016 2 commits
  8. 16 Aug, 2016 2 commits
  9. 12 Jul, 2016 1 commit
  10. 11 Jul, 2016 1 commit
  11. 10 Jul, 2016 1 commit
  12. 06 Jul, 2016 2 commits
  13. 03 Jul, 2016 1 commit
  14. 01 Jul, 2016 1 commit
    • Marin Jankovski's avatar
      Merge branch 'bump-chef-zero' into 'master' · 11853d25
      Marin Jankovski authored
      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
      11853d25
  15. 30 Jun, 2016 2 commits
  16. 29 Jun, 2016 1 commit
  17. 28 Jun, 2016 3 commits
  18. 27 Jun, 2016 5 commits
  19. 25 Jun, 2016 2 commits
  20. 23 Jun, 2016 2 commits
  21. 22 Jun, 2016 1 commit
    • Marin Jankovski's avatar
      Merge branch 'feature/pg-slave-detection' into 'master' · 64e7864e
      Marin Jankovski authored
      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: Rémy Coutable's avatarRémy Coutable <remy@rymai.me>
      64e7864e