Required Data: Assisted Update

Issue

I would like to update my Jenkins instance to the latest release, and would like a customized update plan based on my instance, and a 30 minute update consultation call with a DevOps Support Engineer to discuss the best practices when doing so.

Required Data for an Assisted Update

This article describes how to collect the minimum required information for planning an update.

If the required data is bigger than 20 MB you will not be able to use ZenDesk to upload all the information. In this case, we would like to encourage you to use our upload service in order to attach all the required information.

IMPORTANT : Origin and Destination Product and Packaging must be the same. Otherwise, it would be considered a Migration but not an Update.

Environment

Required Data check list

Support bundle

For each Master and Operations Center that is part of the update, generate and attach a support bundle for each to the ticket. You can refer to this document if you need any help: What is a support-bundle and how to create one

Additionally, for CloudBees Core on Cloud Platforms or CloudBees Jenkins Enterprise 1.x or 2.x, provide also the following information depending on the case:

Assisted update template

In order to gather all the information required data, please download the following template, fill it out and attach it to the Support Ticket. In the following, we explain each of the requested points:

  • Solution: CJP, CJP-CM, CJE 1, CJE 2, CloudBees Core on cloud platforms
  • Source Version: the version that you are currently running
  • Target Version: the version that you want to update to
  • Date/Period: the period when you wish to update your instance
  • Time zone: Time zone you would like to have the 30 minute update consultation call in
  • Cluster Information
    • CJOC: Is there a CloudBees Jenkins Operations Center (CJOC)? What is the version of the CJOC? Number of HA nodes for the CJOC?
    • Masters: Number of masters, versions of those masters, number of high availability nodes for each master
    • Executors: Number of dedicated executors
  • Installation Type: RPM, WAR, DEB, Windows Service, manual script, manually created service, …
  • Backup
    • Strategy: Do you have a strategy for backup? How do you generate a backup? Is it a full backup (copy of the $JENKINS_HOME ?)
    • Storage: Where is the backup stored ? (S3, NAS, NFS, …)
    • Frequency: How often do you backup your instance?
    • Validity: When was the last time you tested the backup?
    • Size: What is the size of the backup?
  • Test Environment:
    • For CJP environments: this is ideally a full test environment with a CJOC and client masters. This will require a test license. But if this isn’t feasible, just having a test master with representative jobs is better than nothing.
    • For CJE/ CloudBees Core on Cloud Platforms: There is ideally a full test/sandboxed environment. Alternatively, this could be a test master which could be updated before other masters.
  • Infrastructure description: Do you have a High Availability setup? Other Infrastructure elements/devices to consider: Load Balancer, Proxy, etc
  • Additional Information: Any additional information that could be relevant to the update (for example existence of a failover environment)
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.