Is there a CUP for each version of UCMDB?
Greetings to all,
Does anyone know why the CUP is not included in the CP?
Why are they working as independents?
Re: Is there a CUP for each version of UCMDB?
CUPs (or Cumulative update package) are released once a new minor or minor-minor version is released and the older version is no longer actively maintained.
For example 10.33 CUP1 was released in February because we no UCMDB version 10.34 or 10.40, we released 11.0. From now on 10.33 we receive only CUPs and the 10.3x branch stops at 10.33.
A CUP contains fixed defects and security fixes, very rarely we deliver enhancements via the CUP release, there are rare occasions though.
UCMDB 11.0 doesn't have any CUP because we released 11.10 and so on. The current RnD logic is to have a quarterly release schedule of minor-minor versions as the latest release notes states this.
A CUP and a CP are totally different concepts and they can't be mixed.
A CUP will update the server and probe code, dependencies or settings.
A CP will update/add the class model, discovery resources (Jython scripts, binaries, adapters, other scripts) or discovery TQLs for example. If you open a CP zip you will notice the subsystems that a CP will touch like datamodel, tql, enrichment, calls, typeDef, etc.
EMEA Technical Success