An error occurred fetching the project authors.
  1. 12 Jun, 2015 1 commit
  2. 11 Jun, 2015 1 commit
  3. 09 Jun, 2015 1 commit
  4. 05 Jun, 2015 3 commits
  5. 03 Jun, 2015 5 commits
    • Marin Jankovski's avatar
      Add a changelog item. · 7af2fbba
      Marin Jankovski authored
      7af2fbba
    • Dmitriy Zaporozhets's avatar
      55715735
    • Dmitriy Zaporozhets's avatar
      Move repository when project is removed · 97ff86e0
      Dmitriy Zaporozhets authored
      Ths commit does next:
      
      * When we remove project we move repository to path+deleted.git
      * Then we schedule removal of path+deleted with sidekiq
      * If repository move failed we abort project removal
      
      This should help us with NFS issue when project get removed but
      repository stayed. The full explanation of problem is below:
      
      * rm -rf project.git
      * rm -rf removes project.git/objects/foo
      * NFS server renames foo to foo.nfsXXXX because some NFS client (think
      * Unicorn) still has the file open
      * rm -rf exits, but project.git/objects/foo.nfsXXX still exists
      * Unicorn closes the file, the NFS client closes the file (foo), and the
      * NFS server removes foo.nfsXXX
      * the directory project.git/objects/ still exists => problem
      
      So now we move repository and even if repository removal failed
      
      Repository directory is moved so no bugs with project removed but
      repository directory taken. User still able to create new project with
      same name. From administrator perspective you can easily find stalled
      repositories by searching `*+deleted.git`
      Signed-off-by: default avatarDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
      97ff86e0
    • Alex Lossent's avatar
      Add option to automatically link omniauth and LDAP identities · dfcea8ed
      Alex Lossent authored
      Until now, a user needed to first sign in with his LDAP identity and then manually
      link his/her account with an omniauth identity from their profile.
      Only when this is done can the user authenticate with the omniauth provider and at
      the same time benefit from the LDAP integration (HTTPS authentication with LDAP
      username/password and in EE: LDAP groups, SSH keys etc.).
      This feature automates the process by looking up a corresponding LDAP person when a
      user connects with omniauth for the first time and then automatically linking the LDAP
      and omniauth identities (of course, like the existing allow_single_sign_on setting,
      this is meant to be used with trusted omniauth providers).
      The result is identical to a manual account link.
      
      Add config initializers for other omniauth settings.
      dfcea8ed
    • Stan Hu's avatar
  6. 02 Jun, 2015 5 commits
  7. 29 May, 2015 9 commits
  8. 28 May, 2015 4 commits
  9. 27 May, 2015 8 commits
  10. 26 May, 2015 3 commits