Documentation office hours - Feb 17, 2022

[MarkEWaite (Mark Waite)]

2022-02-17T18:00:00Z

2022 02 17 Docs Office Hours

Participants

Mark Waite (@MarkEWaite), Zainab Daodu , Alyssa Tong (@alyssat )

Notes

• Jenkins is the Way content merge for jenkins.io - Gavin
  • Jenkins is the Way conversion
    • Wordpress site converted to Asciidoc that we can maintain as code
    • Does not need to be on www.jenkins.io
    • If we add it, we roughly double the size of the www.jenkins.io git repository
      • (60 MB to over 100 MB)
    • Today it is located at jenkinsistheway.io
      • jenkinsistheway.jenkins.io as a separate site and separate repository
      • Redirect the existing wordpress site jenkinsistheway.io to the new location jenkinsistheway.jenkins.io
      • Need to be complete by April renewal
    • Mark to work with the infra to confirm that we can host jenkinsistheway.jenkins.io in the Jenkins infra
      • GitHub repository
      • Site (could be on netlify, elsewhere)
• She Code Africa Contributhon
  • Timeline reminder for Mark Waite
    • Project ideas need to be submitted before end of February
      • See the Project ideas form
    • Jude Wellington is working the agreement for CloudBees funding
      • CloudBees funding is approved internally at CloudBees
    • Still need mentors, open to more project ideas
      • Mark to continue recruiting and promoting
  • Project ideas posted to community.jenkins.io
• News
  • Jenkins 2.335 released with UI improvements and systemd based Linux installer
    • Bug reports are arriving from the UI improvements
    • Bug reports are expected on the Linux installer
  • Jenkins 2.332.1 is coming - March 9, 2022 LTS release
    • UI improvements “phase 1” (plugin manager, tables, etc.)
    • Need a changelog and an upgrade guide
    • First review of a draft next week
• Adding a “Troubleshooting” page
  • Answers to frequently asked questions
  • See the Gavin Mogan question on https://gitter.im/jenkinsci/docs
    I want to make a canned response / jenkins.io page about “It looks like you are having trouble running something locally vs inside of jenkins” with tips on how to compare the results of printenv/export/etc. if i were to put it on jenkins.io, where would i put it, and what would be a good header/title?
    • Wiki has a page like that - can reuse the content
    • Proposed to add “Troubleshooting” page into “System Administration”
    • Should it be an entirely different section in the user guide?
      • More attractive as a separate section at the same level as “System Administration”, move content into it and add content
        • “Obtaining a thread dump”
        • “Diagnosing errors”
    • Nice pull request to start that move (Zainab)
      • Create the new Troubleshooting section
      • Move existing page content to the new location
      • Redirect those two existing pages to the new location
        • See content/welcome.adoc for a redirect example file
          • /doc/book/troubleshooting/diagnosing-errors/ as the redirect destination

[hlemeur (Hervé Le Meur)]

@MarkEWaite

If we add it, we roughly double the size of the www.jenkins.io git repository

• (60 MB to over 100 MB)

The jenkins.io repository size is already over 1Go, might benefit from some git history pruning. (Large files commited in the past)

[MarkEWaite (Mark Waite)]

@hlemeur

The jenkins.io repository size is already over 1Go, might benefit from some git history pruning. (Large files commited in the past)

Thanks for noting the error. When I use du -s -h . in a bare, recently garbage collected clone of the jenkins.io repository, I see that it uses 512M, not 60M like I reported.