1. 17 Jan, 2017 1 commit
  2. 16 Jan, 2017 1 commit
  3. 13 Jan, 2017 1 commit
  4. 12 Jan, 2017 1 commit
  5. 11 Jan, 2017 3 commits
  6. 09 Jan, 2017 5 commits
  7. 06 Jan, 2017 4 commits
  8. 05 Jan, 2017 1 commit
  9. 04 Jan, 2017 1 commit
  10. 30 Dec, 2016 6 commits
  11. 29 Dec, 2016 3 commits
    • iv's avatar
      gitlab: Upgrade to 8.8.9 + start automation of gitlab-backup · 9e01d769
      iv authored
      # Upgrade
      
          * GitLab Software + patches ported to GitLab 8.8.9;
          * Configs synced with upstream and SlapOS-ified;
          * Fix promises due to curl upgrade
      
      @jerome @kazuhiko @kirr: if you have any comments, I would be glad to read them. There is a [demo instance](https://softinst69126.host.vifib.net) you can try.
      
      Check on the demo instance for the Gitlab configuration:
      
      - [x] migrations are all `up`, when running: `gitlab-rake db:migrate:status`
      - [x] promises don't fail (including slow ones)
      - [x] web UI seems fine
      - [x] git clone/fetch/push works well
      - [x] email notifications are sent
      
      and Nexedi edition patches:
      
      - [x] raw blobs download
      - [x] private ones with gitlab-ci token `curl -v https://user:token@testinstance/kirr/test/raw/master/hello.txt`
      - [x] applying patches in merge-request
      - [x] merge as topic in merge-request
      - [x] "Nexedi edition" being present on front page and on page footers with ICP
      - [x] clone protocol is only HTTPS (not SSH)
      
      No changes are made in gitlab-workhorse and gitlab-shell upstream this time, but Nexedi patches and a cherry-picked commit are applied in a merge request on gitlab-ce.
      
      Note: in order to build the gitlab SR, you need to change gitlab-ce repository to my own, as it is not merged yet:
      ```
      --- a/software/gitlab/software.cfg
      +++ b/software/gitlab/software.cfg
      @@ -115,7 +115,7 @@ git-executable = ${git:location}/bin/git
       [gitlab-repository]
       <= git-repository
       #repository = https://gitlab.com/gitlab-org/gitlab-ce.git
      -repository = https://lab.nexedi.com/nexedi/gitlab-ce.git
      +repository = https://lab.nexedi.com/iv/gitlab-ce.git
      ```
      
      # Gitlab backup (pull automation)
      
      The idea is to regularly do a gitlab-backup pull for now, so that later, we can add some code to configure the other gitlab instance (not in production) to pull the created backup repo.
      
      /reviewed-on nexedi/slapos!124
      9e01d769
    • iv's avatar
      gitlab: start automation of gitlab-backup · ae7b4120
      iv authored
        - git-clone and build git-backup sources
        - add a cron job doing `gitlab-backup-pull` every 4 hours by default
        - add instance parameter to change backup frequency
        - add xnice for using less resources while backuping
        - add lock to avoid concurrent calls of backup script
        - add a specific software type `gitlab-export` doing all this instead of in
          `default`; this can be changed in Services > parameters (kirr's changes)
      
      `coreutils`, `grep` and `tar` components are used by `gitlab-backup-pull`
      script, as it is called from a cron and the PATH has to include these
      binaries paths
      ae7b4120
    • iv's avatar
      gitlab: use slapos-cookbook-develop + pin slapos cookbook version · 25acc473
      iv authored
      This is needed until the patch regarding `pidfile` in wrapper.py
      (571d6514) is added to released SlapOS cookbook egg.
      25acc473
  12. 28 Dec, 2016 1 commit
  13. 21 Dec, 2016 1 commit
  14. 20 Dec, 2016 1 commit
  15. 19 Dec, 2016 4 commits
  16. 16 Dec, 2016 6 commits