Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Infra meeting notes as helpdesk releases #3040

Closed
lemeurherve opened this issue Jul 8, 2022 · 5 comments · Fixed by #3041
Closed

Infra meeting notes as helpdesk releases #3040

lemeurherve opened this issue Jul 8, 2022 · 5 comments · Fixed by #3041
Assignees
Labels
enhancement New feature or request helpdesk Infrastructure related issues management in Github

Comments

@lemeurherve
Copy link
Member

lemeurherve commented Jul 8, 2022

This will help us preparing our infra team sync meetings.

Current doc manually completed (last week): https://hackmd.io/71pX8qMWTzOlBfOGOeiV9g

Details

---
tags: meeting, infrastructure
project: infrastructure
---
<!-- markdownlint-disable MD026-->

# 2022-07-05

[:movie_camera: Zoom Meeting Room](https://zoom.us/j/92454301214?pwd=aEVoUi9EanpaakN3L1ZxRlpDQk5Ddz09)
[:calendar: Shared Calendar](https://jenkins.io/event-calendar/)
[:speech_balloon: IRC Chat Room #jenkins-infra](https://jenkins.io/chat/#jenkins-infra)
[:email: Google Group (mailing list) jenkins-infra](https://groups.google.com/g/jenkins-infra)
[🧠 Previous Meeting Notes](https://github.com/jenkins-infra/documentation/blob/main/meetings/2022-06-28.md)

## Attendees

* @dduportal (Damien Duportal)
* @smerle33 (Stéphane Merle)
* @MarkEWaite (Mark Waite)
* @poddingue (Bruno Verachten)

## Announcements :loudspeaker:

1. Weekly: on hold.
    * Jetty 10 upgrade has broken websocket agents
        * Apparently no automated test that checks the failure condition
    * Paused the weekly release pipeline while resolving the regression
    * Tim Jacomb is handling the pause and the restart of weekly release

## Notes :book:

* Done (https://github.com/jenkins-infra/helpdesk/milestone/23?closed=1)
  * Usual maintenance: 3 issues for GitHub permissions + 1 password reset
      * Password reset method from Mark: if we *can* associate their Jenkins account with a GitHub account, ask them to fork a jenkins repo to prove they have access to this GH account.
      * Action: Mark add to the Jenkins password reset runbook
  * [May JVM statistics not available](https://github.com/jenkins-infra/helpdesk/issues/3028)
      * Resulted in a documentation update: https://github.com/jenkins-infra/jenkins-usage-stats/pull/4
  * [CI setup for jenkins-infra/plugin-health-scoring](https://github.com/jenkins-infra/helpdesk/issues/3021)
  * [Cannot apt upgrade Jenkins from 2.348 using pkg.jenkins-ci.org](https://github.com/jenkins-infra/helpdesk/issues/3020)
      * TL;DR. HTTP Host Header and SNI must be the same
      * Allowed us to improve puppet: vagrant with docker now

* Work in Progress (https://github.com/jenkins-infra/helpdesk/milestone/23)
  * [Upgrade to Kubernetes 1.22](https://github.com/jenkins-infra/helpdesk/issues/2930)
      * The 4 clusters are done 
      * Post mortem written but to be reviewed
          * Outage on AKS: PVs based on Azurefile buckets (LDAP + get.jenkins.io)
      * Need to write the next upgrade' issue based on what we learned
      * Need to migrate AKS PV to the new CSI drive
  * [Consider removing embeddable-build-status plugin](https://github.com/jenkins-infra/helpdesk/issues/3013)
      * Only ci.jenkins.io left
      * @lemeurherve is working on the batch pull requests as a courtesy to contributors
  * [enable Development integration in JIRA](https://github.com/jenkins-infra/helpdesk/issues/2985)
      * Need help from jenkinsci admins.
  * [JENKINS-49707] Evaluate retry conditions to improve the stability of the builds ci.jenkins.io pipeline-library triage
      * Delayed since 2 weeks
      * Need to check if Jesse is there so we can do it today or tomorrow, right afetr the weekly 
  * [ci.jenkins.io] Provides both powershell and pwsh on all agent templates ci.jenkins.io 
      * Wip: VM OK but still windows container images todo. 
  * [Migrate updates.jenkins.io to another Cloud](https://github.com/jenkins-infra/helpdesk/issues/2649)
      * WiP: Stephane fighting with network in Oracle. Just solved it 1 hour ago :party: :clap: . Cleanup and full PR to create it from scratch and jump to the next step.
      * Next step: puppet \o/
  * [Require Java 11 infrastructure thread](https://github.com/jenkins-infra/helpdesk/issues/2649)
      * Moving out of milestone because no jenkins-infra team action expected, but keep an eye on it
  * [DockerHub rate limiting](https://github.com/jenkins-infra/helpdesk/issues/2961)
      * Next milestone, it's on @dduportal (nothing done yet)
  * [Replace s390x Ubuntu 18.04 agent with s390x Ubuntu 20.04 agent](https://github.com/jenkins-infra/helpdesk/issues/2983)
      * Next milestone, it's on @en3hD3iMRx6_6IXLNY0Rag  (nothing done yet)
  * [ci.jenkins.io agents are very flaky](https://github.com/jenkins-infra/helpdesk/issues/3031)
      * For the next 2 weeks: set of minor changes, hoping to understand what is going on
      * We have to improve observability: traces, aggregating pods logs
  * [502 proxy error when accessing PR view for jenkinsci/jenkins](https://github.com/jenkins-infra/helpdesk/issues/3029)
 

* New/Important [`infra-team-sync-next`](https://github.com/jenkins-infra/helpdesk/milestone/10)
    * Jfrog slowness: was solved 2 hours after the outage beginning. @dduportal to close it.
    * [Downloads /latest directory out of date](https://github.com/jenkins-infra/helpdesk/issues/3034)

* ToDo (next milestone) (https://github.com/jenkins-infra/helpdesk/milestone/24)

## Action Points :muscle:

<!-- How To: https://github.com/jenkins-infra/runbooks/tree/main/meetings -->
* [ ] Publish this meeting note on [jenkins-infra/documentation](https://github.com/jenkins-infra/documentation) 
* [ ] Publish this meeting record on Youtube
* [ ] Publish a topic in community.jenkin.io with the tag `meeting`

Next meeting note - [2022-07-05](https://github.com/jenkins-infra/documentation/blob/main/meetings/2022-07-12.md) 

@lemeurherve lemeurherve added enhancement New feature or request helpdesk Infrastructure related issues management in Github labels Jul 8, 2022
@lemeurherve lemeurherve self-assigned this Jul 8, 2022
@jenkins-infra-helpdesk-app
Copy link

Heads up @lemeurherve - the "helpdesk" label was applied to this issue.

lemeurherve pushed a commit to lemeurherve/helpdesk that referenced this issue Jul 8, 2022
@lemeurherve lemeurherve added this to the infra-team-sync-2022-07-12 milestone Jul 8, 2022
lemeurherve added a commit that referenced this issue Jul 8, 2022
…3041)

* feat: add a GitHub Action to prepare infra meeting notes as release

Closes #3040

* fix: change default 'next' milestone
@lemeurherve
Copy link
Member Author

Corresponding first (test) release: https://github.com/jenkins-infra/helpdesk/releases/tag/infra-team-sync-2022-07-08_1

@lemeurherve lemeurherve changed the title Releases as infra meeting notes Infra meeting notes as helpdesk releases Jul 12, 2022
@hervelemeur
Copy link

hervelemeur commented Jul 12, 2022

Possible improvments:

  • update existing release if there is one
  • create hackmd note with full template
  • add automation on release events:
    • on publish:
      • create new milestone (could be on "current" milestone close)
      • add new milestone to readme
      • add release to readme

cc @dduportal @smerle33 if you have additional ideas

@dduportal
Copy link
Contributor

That is already a lot of usefull automation, thanks buddy!

@lemeurherve
Copy link
Member Author

First release post-meeting published: https://github.com/jenkins-infra/helpdesk/releases/tag/infra-team-sync-2022-07-12_2

lemeurherve added a commit to lemeurherve/helpdesk that referenced this issue Jan 9, 2023
…enkins-infra#3041)

* feat: add a GitHub Action to prepare infra meeting notes as release

Closes jenkins-infra#3040

* fix: change default 'next' milestone
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request helpdesk Infrastructure related issues management in Github
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants