1. 16 Aug, 2019 2 commits
  2. 07 Aug, 2019 1 commit
  3. 08 Jul, 2019 10 commits
  4. 01 Jul, 2019 1 commit
  5. 26 Jun, 2019 1 commit
  6. 25 Jun, 2019 1 commit
  7. 22 Jun, 2019 1 commit
  8. 29 Apr, 2019 1 commit
  9. 25 Apr, 2019 8 commits
  10. 12 Feb, 2019 2 commits
  11. 16 Jan, 2019 1 commit
  12. 06 Dec, 2018 1 commit
  13. 28 Nov, 2018 3 commits
  14. 26 Nov, 2018 1 commit
  15. 01 Oct, 2018 1 commit
  16. 28 Aug, 2018 1 commit
    • Emanuele Aina's avatar
      Jenkinsfile: Always force specific permission bits · 5f3c4afe
      Emanuele Aina authored
      Using `--no-perms` alone yielded surprising results, such as
      directories with no execute bit set, which could thus not be accessed
      by the web server.
      
      One option would be to use `--no-perms --chmod=ugo=rwX` as suggested by
      the `rsync` man page:
      
      > In summary: to give destination files (both old and new) the source
      > permissions, use --perms.  To give new files the destination-default
      > permissions (while leaving existing files unchanged), make sure that
      > the --perms option is off and use --chmod=ugo=rwX (which ensures that
      > all non-masked bits get enabled)
      
      This would mean that existing files would preserve their permissions.
      But we don't actually care about preserving them, to the contrary we may
      prefer forcing them to a known state such that redeploying from scratch
      would give the same results.
      
      In order to achieve this, set `--chmod=ugo=rwX` in combination with
      `--perms` (implied by `-a`).
      Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
      5f3c4afe
  17. 21 Aug, 2018 1 commit
  18. 25 Jul, 2018 1 commit
  19. 12 Jul, 2018 2 commits