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

ci.jenkins.io: upgrade datadog plugin from 7.x to 8.x #4377

Closed
dduportal opened this issue Nov 6, 2024 · 5 comments
Closed

ci.jenkins.io: upgrade datadog plugin from 7.x to 8.x #4377

dduportal opened this issue Nov 6, 2024 · 5 comments

Comments

@dduportal
Copy link
Contributor

Service(s)

ci.jenkins.io

Summary

Same as #4236

As the past attempts to upgrade the datadog plugin (ref. #4080) did corrupt the Jenkins Home, we have to be careful.

We need to:

  • Check changelog and user feedbacks (as it's been a few weeks since last release)
  • Announce operation
  • Take a backup of the data disk (snapshot)
  • Perform upgrade and check carefully the results
  • Rollback snapshot if any error happens due to datadog

Reproduction steps

No response

@dduportal dduportal added the triage Incoming issues that need review label Nov 6, 2024
@dduportal dduportal added this to the infra-team-sync-2024-11-12 milestone Nov 6, 2024
@dduportal dduportal removed the triage Incoming issues that need review label Nov 13, 2024
@dduportal
Copy link
Contributor Author

Planned for Thursday 14 Nov. (ref. jenkins-infra/status#556)

@dduportal dduportal self-assigned this Nov 14, 2024
@dduportal
Copy link
Contributor Author

Update:

@dduportal
Copy link
Contributor Author

Update:

=> LGTM, let's roll!

@dduportal
Copy link
Contributor Author

Update:

@dduportal
Copy link
Contributor Author

Update:

  • Closing operation on status.jio (Close CI maintenance (datadog 7.x -> 8.x plugin upgrade) status#557)

  • All builds were successful, no ERROR message in ci.jio logs and no corruption

  • Metrics observation: it is a bit soon to draw conclusion but we seem to have a minor CPU usage increase:

    Capture d’écran 2024-11-14 à 09 57 26

    • The "%user" means Jenkins (and other user processes such as Apache) are using a bit more of CPU resources
    • However it seems we have a bit of "%iowait" + "%system" which hints to contention on the block devices level (system disk? data disk?)
    • Note that, since we are moving ci.jenkins.io to AWS with unified disk an better instance capacity (along with arm64 CPU), this should not be a concern at all (modern arm64 CPUs should manage compression better, and wider PCI lanes means less I/O, along with unified block storage device for less interruptions)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant