Configuring a Build Server to Use a Concurrent Build License

Continuous IntegrationLicense Management GuideConcurrent BuildsAutomated Builds

Overview

As a developer, you first need to check your myQNX account to confirm that the administrator has already deployed a Continuous Integration Build Server License for you. If so, you are now a valid licensed developer who can download and install software and are ready to configure your build server.

To configure a build server to use a concurrent build license, create an installation of the QNX Software Development Platform (SDP) and then add the concurrent build license tools package to that installation.

You can create the installation directly on each build server. However, this approach can be time-consuming, especially if you have a large number of servers. A more efficient approach is to create the installation on a staging machine and then use the QNX Software Center's Deploy Installation feature to make that installation available to any number of development hosts. This approach also enables everyone in your development team to work with the exact same QNX SDP configuration.

For details on the Deploy Installation feature, refer to the Creating Deployed Installations of QNX SDP chapter in the QNX Software Center Guide.

Configuration steps

To configure a build server to use a concurrent build license:

  1. Using the QNX Software Center, add a QNX SDP installation to the host.

    For details, refer to the Add, choose, or remove installations chapter in the QNX Software Center Guide.

  2. If you're prompted to enter a license key, either enter a concurrent build license key that QNX provided or select the concurrent build license key from the displayed list.

    Concurrent build licenses are typically deployed through the myQNX License Manager.

  3. For QNX SDP 7.1 or later, skip this step.

    Install the concurrent build license tools package:

    1. From the Welcome screen of the QNX Software Center, select Install New Packages.
    2. Look at the installation selector to make sure you are adding the package to the desired QNX SDP installation.

    3. In the Updates or Available tab, expand the Floating License Utilities group, then expand the Tools subgroup and select Floating License Tools (Windows, Linux, macOS).

      Note:
      To read the package release notes before proceeding with the installation, click the Release Notes item in the Properties pane.
    4. Click Install.
    5. Make sure that the Floating License Tools (Windows, Linux, macOS) item is checked, then click Next.
    6. Review the list of packages that the QNX Software Center will install, then click Finish to start the installation process.

  4. Set up your QNX environment:

    • On a Windows host, open a command prompt window, then run this script from the root of the QNX SDP installation: 
      qnxsdp-env.bat
    • On a Linux or macOS host, open a shell, then run this script from the root of the QNX SDP installation: 
      source qnxsdp-env.sh

  5. Using the QNX Software Center, configure the address of the license server using one of the options below:

    Run the following lmutil command to set up a connection to the license server.
    lmutil lmpath -override qnxlm address_of_license_server
    Or, add the following configuration to the QNX environment:
    To enable Linux or macOS hosts, open qnxsdp-env.sh, add this line, then save your changes: 
    export QNXLM_LICENSE_FILE=address_of_license_server
    To enable Windows hosts, open qnxsdp-env.bat, add this line, then save your changes: 
    set QNXLM_LICENSE_FILE=address_of_license_server

    address_of_license_server should be in the form of port@address, where:

    port
    The port on which the license server listens for connections. If you're using the default port, you can omit port.
    @address
    The hostname or IP address of the server. The @ is required even if port is omitted.
  6. Run qcc, which performs a license check, to test whether your concurrent build license configuration is working properly: 
    qcc

    If the license check succeeds, the qcc command prints no files to process. You can now run the command-line tools (qcc, qdb, mkefs, etc.).

    If the license check fails, refer to the Troubleshooting chapter of this guide for solutions.

Note:
License key persistence

If a development tool signs out a concurrent build license key and then terminates, it holds the key for a few minutes. The key is then released for use by another user. Refer to the Introduction chapter of this guide for more information.

Environment variables related to concurrent build licenses

Env variable Description
QNXLM_LICENSE_FILE The port@host setting for the concurrent build license server that supports QNXLM licenses. Set automatically upon successful checkout. When the build server is in use, you can set it in the Windows registry or, on UNIX, in $HOME/.flexlmrc.
QNX_LICENSE_LINGER The minimum number of minutes the Flex server can retain a license. Default: 5 min.
Note:
You cannot shorten the linger time, but you can extend it to a longer duration.
QNX_LICENSE_QUEUE_INFO Verbose diagnostic for the checkout request. When set to a non-zero value, prints out license queue error messages in stderr. To turn off verbose diagnostic, use QNX_LICENSE_QUEUE_INFO=0.
QNX_LICENSE_QUEUE_TIMEOUT The number of seconds to wait for an available concurrent build license before timeout. Default: 300 s.
Note:

Error conditions:

  • When set to an unparsable or wrong value, defaults to 300 seconds and prints a warning:

    "Invalid QNX_LICENSE_QUEUE_TIMEOUT value: [value], defaulting to 300 s. Only positive numerical value is allowed."

  • When set to zero, fails immediately.
  • When set to a non-zero value while the current license is not Flex-enabled, fails immediately and prints a warning:

    "Cannot find build server key, the value of QNX_LICENSE_QUEUE_TIMEOUT will be ignored."
Page updated: