The CICD Integration now supports a new package manager for dependencies discovery. NuGet was added as the fourth supported dependency manager to the CICD API, to allow wider support of software projects developed in .NET. Dependency files can be sent directly to our API for processing or through the Azure Pipelines plugin.
The Azure pipeline plugin now supports also pipeline setups on Windows machines with the operating systems Windows Server 2016 and 2019. With this addition, the pipeline step that the Azure plugin provides can now not only be executed on Linux-based pipelines but also on Windows-based pipelines. Furthermore, we have added support for the “classic editor” of Azure pipelines which allows the user to configure the build step also on older pipelines.
The GitHub Repository connector can now be set up through our new Integration Hub UI. To enable a GitHub repo scan of your GitHub organization, simply go to the Admin area, select GitHub Repository Connector from the drop-down and add your GitHub token and you are good to go. If you want the integration to run regularly you can also provide an individualized schedule on which the integration will run. For more details please reach out to your Customer Success Manager.
We have improved the logging for the Jenkins Plugin, allowing users to see in more detail if something went wrong and debug plugin configuration more effectively. Therefore, the LeanIX Log in the plugin now displays error messages and codes from the CI/CD API it connects to directly. This makes it easier to determine whether the problem originates from authentication, the data being sent, or the plugin configuration.
On the Deployment Fact Sheet we have added a new section called "Kubernetes". Here, deployment data is written into targeted attributes such as Update Strategy, Number of Ready Replicas, Labels, Limits, Requests, and Annotations. These attributes can be filtered in the inventory or in reports.
We’re excited to announce two new out-of-the-box integrations with Azure Pipelines and GitHub, making it easier to catalog and navigate the owners and dependencies of services in your DevOps toolchain.
Today, we released Microservice Intelligence (MI) to be generally available. MI discovers and catalogs services running on Kubernetes, Jenkins, and GitHub Actions and establishes a 360-degree view of all cloud-native applications, ownership, and dependencies. Knowing where microservices are deployed, who is responsible, and how they support the business enables engineering teams to control complexity, boost developer productivity, and build reliable software.