I’m building DevOps automation for a remote (private cloud) deployment to stand up a build home on the IMS without manual intervention on the configuration files. The idea is to take as many steps out of the process as possible to both speed it up and make it more repeatable and reliable, like reading passwords from an internally encrypted source. (Building in one step is an important best practice.) I’m excited that the mature technology stack of IFS Cloud makes this possible for the very first time!

The version numbers for the application, the remote bootstrap file, and the remote bootstrap binaries file all disagree. For example, application version 24.2.4 calls for remote bootstrap version 2.12.9 and remote bootstrap binaries version 2.7.3. Why are the version numbers different? You must have needed a really good reason to not make these obvious and just name them according to the application version, even if that means duplicating the same file with two names, like remote bootstrap 2.12.11 which works with both 24.2.5 and 24.2.6. I know such duplication was common in earlier versions, but now it’s more of an exception.

I want to make sure that my mental model of how everything fits together is compatible with the philosophy under which IFS is operating internally.