Executing repotools that are not supported by the Engineering Lifecycle Management operator

Administrators and support team run the repotools in the Engineering Lifecycle Management on Hybrid Cloud containers when the Engineering Lifecycle Management server is running. Admins can enter a list of repotool commands and repeat them across all Engineering Lifecycle Management instances by using the repotool scripting. Engineering Lifecycle Management on Hybrid Cloud operator doesn’t support some repotools and such repotools can be executed through application pods.

Steps to execute repotools command not supported by Engineering Lifecycle Management on Hybrid Cloud operator

For executing repotools command not supported by Engineering Lifecycle Management on Hybrid Cloud operator, following are the steps to execute such commands through application pods.

  1. Determine the mode in which the command is to be executed (online or offline)
  2. Determine on which pod the command needs to be executed (applications that support repotools command)
  3. Login to the pod of the specific application.
  4. Follow the commands for online or offline execution:

offline mode

  1. Stop the Application Server
    Offline mode requires down the application server or stopped before the execution of the repotools command. By running the following command, it keeps the pod liveness probes active that makes container in a live state and eventually pod doesn't get restarted by the kubelet.
    /elm/server/addServerTask.sh afterShutdown REPOTOOLS_VERIFY
/elm/server/server.shutdown
  2. Execute the Repotools command

    Replace the placeholders for <app_name>, <repotool_command>, and <arguments> with the application name, repotool command name, and arguments used.

    /elm/server/repotools-<app_name>.sh <repotools_command> \
<arguments/parameters> \
logfile=/elm/server/conf/<app_name>/logs
    running repotools command verify on JTS
    /elm/server/server.shutdown && /elm/server/repotools-jts.sh -verify \
teamserver.properties=/elm/server/conf/jts/teamserver.properties \
logfile=/elm/server/conf/jts/logs/repotool-jts-verify.log
    Note: logfile argument is mandatory to set the path within the /elm/server/conf location as it is the PVC mount location. Start the application server
  3. Start the Application Server 
    /elm/server/server.startup

online mode

  1. Execute the Repotools command

    Replace the placeholders for <app_name>, <repotool_command>, and <arguments> with the application name, repotool command name, and arguments used.

    /elm/server/repotools-<app-name>.sh <repotools_command> <arguments>
    /elm/server/repotools-jts.sh onlineVerify \
repositoryURL=https://example-elm.ibm.com/jts adminUserId=example adminPassword=example