This article provides a step-by-step guide on how to set up Azure DevOps pipeline tooling for continuous integration and deployment of GeneXus Knowledge Bases.
Before you begin, make sure you have access to an Azure DevOps organization or personal project. This is essential to create repositories, pipelines, and configure agents.
For more information on the registration process, refer to the official documentation:
Azure DevOps, developed by Microsoft, offers a wide range of features and is natively integrated with tools like GitHub and Visual Studio.
However, it is also flexible enough to work with other development tools, including GeneXus. This table of contents outlines one approach to integrating Azure DevOps with GeneXus.
Azure DevOps provides multiple capabilities that support various roles, from project management (using Boards and Kanban diagrams) to automation and centralized source code management.
It enables version control and collaborative development through Azure Repos.
This table of contents focuses specifically on Repositories and Pipelines in the examples that follow.
Steps overview:
- Configure an agent pool: An agent is required to execute the pipeline tasks.
- Create a New project in the Azure DevOps console: This project will contain your repositories, pipelines, and build artifacts.
- Create a Git Repository for pipeline and resource synchronization: This repository will store your YAML pipeline scripts and other required files.
- Configure the pipeline script with KB/Server info and credentials: Define the build steps, including the MSBuild tasks, and specify the connection details to your GeneXus Server and Knowledge Base.
Once your synchronization setup is complete, you may choose one of the deployment alternatives that best suits your Knowledge Base requirements and execute the corresponding MSBuild tasks, as described in the Deployment Scenarios section.
Note: It is recommended to involve a DevOps or pipeline expert when designing and maintaining Azure DevOps pipelines. The examples provided in this table of contents serve as a general starting point and may require adaptation based on the specific needs and complexity of each project. While these examples offer useful guidance, they are not intended to cover all scenarios or replace specialized expertise.