[]
MESCIUS licensing is based upon the development machine. However, in a pipeline environment, the license needs to be activated on a virtual machine or docker on the cloud. A pipeline license is designed for the build agent of DevOps pipelines like Azure, AWS, and Bitbucket. If your pipeline has a dynamic agent (for example, Azure pipeline with Microsoft-hosted agents) you must activate the license before each build and deactivate the license after each build and, depending on the type of license, you may need to deactivate the license after each build. See the instructions below for your type of license.
This method of activation is the recommended one.
With a pipeline license you may build and deploy applications from a dynamic build agent with fewer limitations than a standard developer license. A pipeline license allows unlimited activations per day with no need to deactivate the key. The serial key must still be activated before each build, but it does not require network access and it cannot be used for design-time development.
You should contact our sales team at activereports.sales@mescius.com or call 1.800.858.2739 for issuing the pipeline license. A pipeline license includes three things:
To activate your pipeline serial key on the build server follow these steps:
Install the MESCIUS License Manager tool in the pipeline.
Linux/MacOS: https://www.nuget.org/packages/GrapeCity.LicenseManagerTool/ or you may install the gclm tool from command line:
dotnet tool install -g GrapeCity.LicenseManagerTool
Copy the Local Activation Package file to the gclm install location.
Before the build, call the gclm tool to activate the license using your serial key and provided password.
Windows:
C:\ProgramData\GrapeCity\gclm\gclm.exe "437d0240-ba2c-4f9e-9a92-c2816f83d391" -a "key" “password”
Linux/MacOS:
gclm "437d0240-ba2c-4f9e-9a92-c2816f83d391" -a "key" “password”
type=note
Note: You may also perform the activation (step 3) using the MESCIUS License Manager GUI if command line interface is not required. See Licensing a Developer Machine and follow the steps for activating your pipeline key. It will prompt you to enter the password separately.
With a standard developer license you may build and deploy applications from a dynamic build agent with some limitations.
To activate your serial key on the build server follow these steps:
Linux/MacOS: https://www.nuget.org/packages/GrapeCity.LicenseManagerTool/ or you may install the gclm tool from command line:
dotnet tool install -g GrapeCity.LicenseManagerTool
Windows:
C:\ProgramData\GrapeCity\gclm\gclm.exe "437d0240-ba2c-4f9e-9a92-c2816f83d391" -a "key"
Linux/MacOS:
gclm "437d0240-ba2c-4f9e-9a92-c2816f83d391" -a "key"
Windows:
C:\ProgramData\GrapeCity\gclm\gclm.exe "437d0240-ba2c-4f9e-9a92-c2816f83d391" -d
Linux/MacOS:
gclm "437d0240-ba2c-4f9e-9a92-c2816f83d391" -d
Notes:
To check whether the license is activated or not, follow these steps:
Create a file, say 'info.txt' with the product name and GUID specified
C:\ProgramData\GrapeCity\gclm>gclm "437d0240-ba2c-4f9e-9a92-c2816f83d391" > "info.txt"
Check the license details: license status, license type, serial key, activation date, expiration date, and edition
C:\ProgramData\GrapeCity\gclm>more info.txt