AE build numbers changed: Different build numbers for one component

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

Bob - The AE Builder

Introduction

Since the beginning of the Automation Engine software, its build process was automated with the Automation Engine. That means building any release - regardless if it’s a developer build, a service pack or hotfix build, a new release, etc. - is orchestrated and executed using the AE itself.

It's in the nature of things, that processes which were enhanced and juggled over years, became weaknesses. Other disadvantages became visible, because it was not state of the art any longer. Therefore the whole process was completely renewed and is now internally referred to as “Bob”.
Only the tool which is used for the whole build process is the same – it’s again the Automation Engine!
 

Change

For an Automation Engine user this doesn’t change anything at all. However, users which are acting as administrator of the AE might notice that the Automation Engine version indicators of all Automation Engine components have changed.

Actually this was not the first time in the history of this software product. The current and some previous version indicators are descripted in the documentation:
https://docs.automic.com/documentation/webhelp/english/AWA/12.0/DOCU/12.0/AWA%20Guides/help.htm#AE_AWA_Source/RelNotes_RichClient/ucaaxj.htm

However, this time the change has an additional dimension.
Up to now one AE component had one version indicator / build number. Now components, like the Engine itself, can have multiple different build numbers for different files within one release.
 

Example

In version 12.0.0 (old build process) the Automation Engine has the build number “12.0.0+build.3456”, regardless if a CP, WP or JWP is observed.
In version 11.2.4(new build process) on the Automation Engine different build numbers can be seen, for the CP “11.2.4+build.1014”, for the WP “11.2.4+build.16886” and for the JWP “11.2.4+build.2956”:

<Please see attached file for image>

Even though build numbers are different, they belong to the same version – identified by “Major.Minor.Service_Pack” being the same – so they are compatible. In this case: “11.2.4” is the same for all server processes.
That means as long as the Major Release, Minor Release and Service Pack number is the same, everything is fine and there is no need for any concern!
 
Note: In case of a hotfix version the Service Pack is followed by “+hf.n”, e.g.: “12.0.1+hf.2.build…”:

<Please see attached file for image>

 

Conclusion

For an Automation Engine user the last number of the version indicator, the build number (+build.nnn), can be ignored! It is solely used for internal purposes.
 

versions.csv

For each release of the Automation Engine an image is assembled, it contains all AE components. For service pack and hotfix releases most likely only some components have changed. So the image may contain components of different service packs or hotfixes.
To keep an overview, which components changed or which service pack / hotfix version of a component is included the so called versions.csv file is added.
Up to now the complete version indicator was included. Since the last number of the version indicator can be different for the same component it will not be listed in the version.csv any longer.
 

Exmaple

Old style of versions.csv:

<Please see attached file for image>

New style of versions.csv:

<Please see attached file for image>

 

Environment

Release: AUTWAB99000-11.0-Automic Workload Automation-Base Edition
Component:

Resolution

See description.