KBEC-00450 - CD Assisted Update

Article ID:360044856572
3 minute readKnowledge base
On this page


Customers looking for help in upgrading their CD system can request help from Support.
This document outlines some details that will be beneficial to collect in advance of making such requests.


We recommend an “Assisted Update” be considered for all customers to help guide them through CD system updates to make the process easier and safer.

This process allows a CloudBees Development Support Engineer to review your instance and prepare a customized update plan which contains:

  • A summarized list of known potential issues you may encounter during your update, based on your current version, target version, remote agents, and what we have experienced with other clients running through similar updates

  • Analysis of known issues your CD instance(s) are encountering, or may encounter after performing the update

  • Best practice recommendations on how to test before starting the update on production

  • Steps to follow when performing the production update

  • Recommendations regarding backups to help with any recovery process, should that prove necessary along the way.

  • A 30 minute consultation call to explain the update notes and give you a chance to ask any questions you may have regarding your update

If you are interested in this process, the next step would be to provide us the Required Data for an Assisted Update (below) on a new support ticket. This should include the timezone where you are located, and estimated time when you will perform the upgrade, so we can have the Engineer in the most appropriate timezone assigned to your request.

Requested data for an Assisted Update

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

If any requested data files are larger than 50 MB you will not be able to use ZenDesk to upload all the information. In this case, we would encourage you to use our upload service in order to attach all required information.

IMPORTANT : Origin and Destination Product and Packaging must be the same. Otherwise, this effort would be considered a Migration and those details should also be identified.

Required Data checklist

In order to gather all the information required data, please copy and paste the following set of questions into your favourite text editor, fill it out and attach it to a Support Ticket.

  1. What is your target date for performing your upgrade?

  2. Current CloudBees CD (CloudBees Flow) Version

  3. Please list any hotfixes applied to this version, if any?

  4. Target CloudBees CD (CloudBees Flow) Version

  5. OS in use for CloudBees CD (CloudBees Flow) Server(s)

  6. Are any additional services running on your Server Machines?

  7. What is the current amount of free disk space on each CD Server?

  8. What DB is used for this system?

  9. What is the current DB version?

  10. Is this DB running on a separate machine from the CD Server machine(s)?

  11. Do you have an assigned DBA for your system?

  12. If you have a diagram representation of your existing architecture, passing this diagram forward can be beneficial for future communication

  13. Do you have a comparable test environment?

  14. Do you intend to test this upgrade in TEST before affecting production?

  15. Are you planning on changing any machines in your environment during this upgrade?

  16. If so, which ones?

  17. If any of the server components rely on Kubernetes, please list which ones here:

  18. What is your regular backup process?

  19. How are those backups collected?

  20. How often are these backups taken?

  21. Please provide the output results from these commands for each CD Server in your architecture:

    ectool login admin

    ectool getServerStatus --diagnostics 1

  22. Please provide the most recent commander.log files (ideally the last 1 hour worth of coverage)

  23. Where are your plugins stored today?

  24. Does this match with what is stored as shown in the UI under: Administration -→ Server -→ Settings?

  25. If this update includes a migration, please list any components and OS changes involved