
|
Variable
|
Description
|
||
|
SCM_DIR
|
The path to the scmloop[ .bat] script itself.
|
||
|
CB_BASE_URL
|
The base URL of the Codebeamer web application. For example: http://localhost:8080/cb.
|
||
|
JAVA
|
It must point to the java executable of the JRE to use.
|
||
|
SCM_TOKEN
|
Since Codebeamer release 2.0.0.1.
The SCMLoop token has been introduced to prevent unauthorized calls towards the Codebeamer SCM repositories.
The token can be found
• In the Application Configuration, under the "scc" node:
"scc" : {
In the Application Configuration, the token is automatically generated and encrypted. If you delete the token and click Save, the token is automatically regenerated.
If you add a new, decrypted token and click Save, Codebeamer saves and automatically encrypts the new token.
• In the CB/repository/scmloop/scmloop file of the locally installed Codebeamer instance where the decrypted token is stored.
If only internal repositories are used, no token management is required from the user. Codebeamer automatically generates the token during the first installation, and automatically edits the SCMLoop script.
The token generation and the editing of the SCMLoop script are also performed when upgrading Codebeamer.
If you use external SCMLoop installations,
1. You must overwrite the token at least once in the application_configuration.
2. Store the unencrypted form of the token.
3. Set the SCM_LOOP environment variable to the unencrypted form of the token in the shell script of the external SCMLoop installation.
When upgrading Codebeamer, the existing external SCMLoop installations must be updated as the old clients cannot send the token.
|
) and add hg to the PATH. On Windows use: setx PATH %PATH%;MERCURIAL_HOME.