RTC/BF integration: updating password
With about 75 build definitions in RTC using the RTC-BF integration,
quarterly password changes are a small nightmare. In BF, the server auth concept allows the username/password to be stored and changed in one place and referenced in all the builds, but in RTC, every build definition has its own copy of the BF user/password. In my situation, being able to define the BF username/password in the RationalBuildForgeConnector build engine would suffice but I'm sure not everyone uses one BF account for all builds in one RTC repository so that probably isn't a general solution. Perhaps a notion of multiple "virtual" RationalBuildForgeConnector instances to afford setting properties on groups of builds? I digress... Is this by any chance "fixed in 3.0?" If not, and given it's too late for a feature request, is there some other means of updating the password in a group of builds without opening each one and doing it from the GUI? |
One answer
Hi Michael,
In 3.0, we now capture the Build Forge connection info in the engine, so it can be shared with multiple definitions. You're also no longer constrained to having just a single, specially named, one like RationalBuildForgeConnector. For example, different projects or teams could each have their own BF engine describing a different connection, possibly to the same BF console but with different credentials. For more on this, see: https://jazz.net/wiki/bin/view/Main/RationalBuildForge/RTC3M7BFIntegrationEnhancements and the other BF integration enhancements in 3.0 described at: https://jazz.net/wiki/bin/view/Main/RationalBuildForge |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.