We now use a coding assistant (Claude Code) to assist with upgrade planning and execution. The provides a number of benefits:
- better upgrade path planning to account for needing to manage php version, each extension's espo minimum compatibility, and compatibility with our customizations.
- automation of the upgrade itself, including espo core and all extensions.
- automated testing.
- fewer compatibility surprises & associated rollbacks .
- large reduction in cost (man-hours).
Prior to this, upgrading was subject to unforeseen compatibility problems and quite time consuming. We're on a docker environment, using some of the paid extensions. Upgrades tend to be infrequent, in part because it's a "project" and no one is dedicated to this, so we're always behind.
One of the difficulties is the agent's lack of access to all extension manifests. Currently the set of extension releases have to be downloaded manually to the host environment. It would be better if the manifests were available in a repo that can be accessed by the agent. While the manifests occasionally have mistakes, they are essential.
Even better if the extension code for all releases is available in a private repo for us paid users, with a git access key. The agent has been able to identify issues in the extension by version as a result of viewing the code itself. Examples: manifest errors, our heavily customized use of Sales Pack, our back office server that uses espo Api calls, and our in-house developed espo mcp server.
Appreciate your consideration.
- better upgrade path planning to account for needing to manage php version, each extension's espo minimum compatibility, and compatibility with our customizations.
- automation of the upgrade itself, including espo core and all extensions.
- automated testing.
- fewer compatibility surprises & associated rollbacks .
- large reduction in cost (man-hours).
Prior to this, upgrading was subject to unforeseen compatibility problems and quite time consuming. We're on a docker environment, using some of the paid extensions. Upgrades tend to be infrequent, in part because it's a "project" and no one is dedicated to this, so we're always behind.
One of the difficulties is the agent's lack of access to all extension manifests. Currently the set of extension releases have to be downloaded manually to the host environment. It would be better if the manifests were available in a repo that can be accessed by the agent. While the manifests occasionally have mistakes, they are essential.
Even better if the extension code for all releases is available in a private repo for us paid users, with a git access key. The agent has been able to identify issues in the extension by version as a result of viewing the code itself. Examples: manifest errors, our heavily customized use of Sales Pack, our back office server that uses espo Api calls, and our in-house developed espo mcp server.
Appreciate your consideration.
Comment