AutoBuilder setup functionality is broken since end of September 2022

Hi,

since end of September it’s not possible anymore to properly setup IFS AutoBuilder from \\corpnet\files\F1Tools\IFSAutoBuilder

There are 3 reasons for this:

• The configuration part has split into 3 sub parts (LKP, CMB, MKE) which renders the setup routine unusable as the configuration file SetupBuildAutomation.xml does not hold the correct paths for the IFS ConfigBuilder anymore. Check the following XML tags:

 <CONFIGBUILDER_SOURCE>..\IFSConfigBuilder\SetupConfigBuilder_Apps8.exe</CONFIGBUILDER_SOURCE>   <CONFIGBUILDER_SOURCE80>..\IFSConfigBuilder\SetupIFSConfigBuilder80.exe</CONFIGBUILDER_SOURCE80>

  <CONFIGBUILDER_SOURCE90>..\IFSConfigBuilder\SetupIFSConfigBuilder90.exe</CONFIGBUILDER_SOURCE90>

  <CONFIGBUILDER_SOURCE100>..\IFSConfigBuilder\SetupIFSConfigBuilder100.exe</CONFIGBUILDER_SOURCE100>

As you can see, there’s only “..\IFSConfigBuilder\...”. As CoS has now put everything into an additional subdirectory structure, this will fail during setup. The configuration XMLs need to be updated properly to “..\..\IFSConfigBuilder\..” in order to make this working again.

• All new AutoBuilder users (dseabwws, etc.) are not properly configured for CxBP Harvest environments. They can’t list up all the Harvest environments during the AutoBuilder setup. It’s impossible to select my customer in the list as it stays empty. The old AutoBuilder user (aubuwws) was able to do this and this has to be fixed for all Harvest Brokers including CxBP
• It’s VERY likely that the new AutoBuilder users are not able to properly mount directories during a Remote Build (for BnT). We’ve had this with every CxBP customer lately and it always had to be fixed manually by CoS. Hence this needs to be verified by CoS that those new users have the same grants and rights inside all of our VMs

Last but not least, there’s no information on how long the old aubuwws user will stay active. This user is configured in dozens of our customer environments and if this user is disabled, every AutoBuilder instance needs to be entirely re-setup. Please update us on this!

Best regards
Markus Albrecht