Build Tasks for the Matrix42 Extension Gallery

Matrix42 offers an extensions gallery for the Matrix42 Digital Workspace Platform. Customers using Azure DevOps as Application Lifecycle Management platform can use the following build tasks to implement a fully automated publishing process:

• Generate Package
• Upload Release
• Publish Release

Should you have any questions please contact support@matrix42.com.

Generate Package

The Generate Package task allows to pack all artifacts into the solution builder configuration package form. The whole package is driven by a package.json which should be stored in the source code repository as well. The Generate Package buidl task is able to override the version number managed in the package.json by adding a build numnber to make every CI build unique.

We are recommending the following repository structure:

• BasePackage: The folder BasePackage contains the content of the generated Configuration Packaged directly exported with the export action in the Matrix42 Digital Workspace Platform.

• Solutions: The folder Solutions should contains all Visual Studio Projects to build libraries which will become part of the Configuration Package. Finally the Generate Package activity will inject the libraries correctly.

Upload Release

The Upload Release activity allows to upload a generate Solution Builder Configuration Package to the Matrix42 Extension Gallery and prepares easily the release process controlled in the Extensions Management portal or with an Azure Release Pipeline.

Publish Release

The Publish Release activity allows publishing a previously uploaded Solution Builder Configuration Package. We highly recommend using this activity in an Azure DevOps Release Pipeline to reflect the different release states, for instance, when implementing ring based deployment.

Basic Azure Pipeline

The following screenshot shows exemplary an Azure Buid Pipeline generating a Configuration Package and uploading this package to the Matrix42 Extension Gallary:

The generate package activity expects the location of the package.json file in the source code repository and allows to inject addditonal files and directories. The additional directories should be the output directories in the build solutions. More information about the structure of a configuration package is available in the Matrix42 Online Help - https://help.matrix42.com.

The second step is the upload of the generates package into the Matrix42 Extensions Gallery. The system supports a service connection to manage the secrets for the extension gallery. After selecting the collection the right extensions-id neesd to be set and the upload will work at ease. Uploading an extension measn NOT publishing the extension so the Matrix42 Extension Gallery can be used as artifact sink at all.