SCM.exe and Passwords
One answer
Unfortunately, JBE and the SCM CLI use different mechanisms for managing credentials. The SCM CLI does not understand the password file format used by JBE. The solution is to login manually with the SCM CLI before running JBE, using the same credentials as used by JBE, then from the build script invoke the SCM CLI without credentials.
JBE does understand the repositories file format used by the SCM CLI. This file is normally in ~/.jazz-scm/repositories.txt. You can indicate this file on the JBE command line with -repositories. You still need -repository to indicate the primary repository, but should exclude credential options like -userId, -pass, -passwordFile as it will get the user id and password from the repositories file. This approach is required when using multiple repositories (i.e. for distributed SCM). This was also discussed in thread https://jazz.net/forums/viewtopic.php?t=21064
For other info about using the SCM CLI in builds, see article:
https://jazz.net/library/article/195
JBE does understand the repositories file format used by the SCM CLI. This file is normally in ~/.jazz-scm/repositories.txt. You can indicate this file on the JBE command line with -repositories. You still need -repository to indicate the primary repository, but should exclude credential options like -userId, -pass, -passwordFile as it will get the user id and password from the repositories file. This approach is required when using multiple repositories (i.e. for distributed SCM). This was also discussed in thread https://jazz.net/forums/viewtopic.php?t=21064
For other info about using the SCM CLI in builds, see article:
https://jazz.net/library/article/195