# Documentation office hours - Feb 25, 2022

**URL:** https://community.jenkins.io/t/documentation-office-hours-feb-25-2022/1775
**Category:** Community
**Tags:** meeting, sig-docs
**Created:** [March 11, 2022, 1:07am UTC](https://community.jenkins.io/t/documentation-office-hours-feb-25-2022/1775 "2022-03-11T01:07:44Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)
#### Post date: [March 11, 2022, 1:07am UTC](https://community.jenkins.io/t/documentation-office-hours-feb-25-2022/1775/1 "2022-03-11T01:07:44Z")

</div>

2022-02-26T02:00:00Z

[![](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/f/fa5544a3aab3487133b336b290160b16b22fa995.jpeg "2022 02 25 Docs Office Hours") ](https://www.youtube.com/watch?v=i5p_GhqGo-U)

**Participants**

Mark Waite (@MarkEWaite), Dheeraj Singh Jodha (@dheerajodha) , Meg McRoberts, Kristin Whetstone

**Notes**

- News
  - Jenkins 2.336 released with several fixes for image and icon issues
    - Thanks to Docs office hours for changelog review

  - Jenkins 2.332.1 release candidate available for testing
    - UI improvements
      - Tables
      - Manage Jenkins
      - Plugin Manager

    - May include [Linux installer based on systemd](https://groups.google.com/g/jenkinsci-dev/c/mRxFPGfuljA/m/y7Rb96V5AgAJ)
    - Changelog and upgrade guide needed

- Interactive tests that Jenkins performs prior to a weekly release?
  - At Dheeraj’s employer, there are interactive tests that are described
    - Step-wise test cases to confirm things are functional

  - Does Jenkins have those types of descriptions of test cases?
    - No, we don’t have those types of descriptions
      - Refer to James Bach, Michael Bolton, Cem Kaner
      - Association for Software Testing (AST) has courses
        - Foundations of Software Testing
        - Bug Advocacy
        - Test Design

    - What should / could we do differently to detect issues sooner?
      - 2.335 had several bugs in visual elements
        - [JENKINS-67828](https://issues.jenkins.io/browse/JENKINS-67828)
        - [JENKINS-67823](https://issues.jenkins.io/browse/JENKINS-67823)
        - [JENKINS-67837](https://issues.jenkins.io/browse/JENKINS-67837)
        - [JENKINS-67832](https://issues.jenkins.io/browse/JENKINS-67832)
        - [JENKINS-41218](https://issues.jenkins.io/browse/JENKINS-41218)
        - [JENKINS-67772](https://issues.jenkins.io/browse/JENKINS-67772)

      - Could we open every web page and check for broken images?
        - Find a broken image detector for authenticated web pages

      - Could consider more layers of tests (do some things only weekly)
      - In many cases, we need specific plugins in order to see the issue
        - Need to have “interesting configurations” that are easy to start and stop
          - Gavin Mogan has his interesting configuration
          - Mark Waite has his interesting configuration

    - We have regular “explorers” who use the UI and report issues
    - We have regular pull request reviewers who check pull requests are ok

  - Interactive tests that are performed by people before weekly releases

- Linux installers switch from System V init to systemd
  - Needs a documentation page, “Managing systemd services”
    - Where does it belong?
      - In the System Administration

    - What topics should be covered?
      - Reloading service definitions
      - Registering services
      - Viewing service configurations
      - Overriding service configurations
      - Starting services
      - Stopping services
      - Reading service logs
      - Pruning service logs

    - What reference documentation could we consider?
      - [Original systemd documentation](https://www.freedesktop.org/wiki/Software/systemd/)
      - [Red Hat Enterprise Linux 7 docs](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/chap-managing_services_with_systemd)
      - [DigitalOcean Tutorial](https://www.digitalocean.com/community/tutorials/how-to-use-systemctl-to-manage-systemd-services-and-units)

  - See [Jenkins developer mailing list proposal](https://groups.google.com/g/jenkinsci-dev/c/mRxFPGfuljA/m/y7Rb96V5AgAJ)
  - Should we have a “Managing Jenkins on Linux”?
    - Mark tends away from this one because of how broad it is

- Google Summer of Code
  - Pipeline steps documentation generator project idea
    - Exploring the current code base
    - Wanted to run it inside the debugger to see what was happening
      - Can it be run in a debugger?
        - Had an error in his Eclipse debugger

      - Mark uses Apache Netbeans, thinks that he ran it in the debugger
      - Kristin uses Visual Studio Code, not in debugger
        - Used the logger facility

- She Code Africa Contributhon
  - Mark to submit [project ideas](https://community.jenkins.io/t/she-code-africa-contributhon-2022/253) before end of February
    - Project manager mentored by Mark Waite
    - Inclusive naming initiative changes for popular plugins
    - Screenshot updates for [www.jenkins.io](http://www.jenkins.io)
    - Test the tutorials, report issues, improve the tutorials
    - Consider “Troubleshooting” as a section worked by a team

  - Need mentors available during Africa daylight hours

- Adding a “Troubleshooting” section to User Handbook
  - Trying an operation in Jenkins fails, works from the command line
    - Selenium tests
    - Operating system user specific tests
    - PATH specific conditions
    - …

  - Zainab will submit a pull request to start that move

- 2.332.1 changelog and upgrade guide