1. 24 May, 2020 3 commits
  2. 14 Apr, 2020 1 commit
  3. 08 Apr, 2020 2 commits
  4. 04 Apr, 2020 1 commit
  5. 02 Apr, 2020 4 commits
  6. 28 Mar, 2020 2 commits
  7. 26 Dec, 2019 1 commit
    • intrigeri's avatar
      Jenkins: move design doc out of the blueprint · 0bb5105c
      intrigeri authored
      A blueprint is a great place to draft stuff while we develop it, but once it's
      deployed in production, a non-blueprint, more stable place, is more suitable.
      For example, it better reflects the fact this doc is about what we're actually
      running, rather than about ideas we've had in the past and might have
      implemented or not.
      0bb5105c
  8. 12 Nov, 2019 6 commits
  9. 19 Sep, 2019 1 commit
  10. 18 Sep, 2019 1 commit
  11. 05 Aug, 2019 3 commits
  12. 03 Aug, 2019 1 commit
  13. 11 Jul, 2019 2 commits
  14. 11 Mar, 2019 1 commit
  15. 29 Dec, 2018 3 commits
  16. 08 Nov, 2018 1 commit
  17. 04 Oct, 2018 1 commit
  18. 06 Sep, 2018 1 commit
  19. 18 Dec, 2017 2 commits
  20. 28 Nov, 2017 2 commits
  21. 26 Nov, 2017 1 commit
    • intrigeri's avatar
      Clarify sysadmin doc about Git repositories for Puppet modules (refs: #14613) · 761c577f
      intrigeri authored
       - Document the authoritative place for our Puppet modules
         and the synchronization mechanism to the public mirrors.
       - Clarify what's the manifests repo and its use of submodules.
       - Avoid pointing non-sysadmins to doc that won't work for them.
       - Point to the Puppet modules Git repo doc from contribute/how/sysadmin.
       - Make the link to our Puppet code more obvious on
         contribute/working_together/roles/sysadmins
      761c577f