Damien Coraboeuf

Going full agentic

Yontrack development has a long history. It started with version V1 around 2010, and then went through many versions: * V2 - new UI, where Yontrack acquires its distinctive look and API * V3 - modern stack, switching to PostgreSQL, GraphQL * V4 - going enterprise level, auto-versioning, auto-promotions * V5 - Next UI, modern authentication,

Yontrack MCP server is available

The Yontrack MCP server is available as an open-source and free component at https://github.com/yontrack/yontrack-mcp/. Easy to plug in in Cursor, Claude or your IDE, you can also host it yourself (Helm or Docker). You just need an API token to connect to your Yontrack

MCP server from scratch - impressions

For builds that have been promoted to RELEASE, can you show me the time it takes to go from the build creation to the promotion? Can you also display the time it takes to go from Bronze to Release? Last week, I wrote a piece about the links between having

Data layer versus API

I recently experimented with creating an MCP server in front of a live instance of Yontrack.

After having plugged it into Claude, I could directly access the Yontrack data and display the information I needed.

For example: Can you give me the durations between the build creation and their BRONZE

Auto versioning on promotion

Whenever you have components which depend on others, there are many ways to upgrade them. This could be as simple as holding a version string in a file. This would typically the case in GitOps driven deployments. So how do you upgrade these versions? Easy right? You open a pull

A journey to Ontrack SaaS

Since Ontrack has been created some years and years ago, the product has grown in features and integrations. This can now be used from the collection of delivery metrics to really drive your automation using for example auto versioning on promotion or delivery metrics. While it's always been

Ontrack delivery metrics

Whether your ingest data from your pipelines in Jenkins [https://nemerosa.ghost.io/2021/10/11/ontrack-from-jenkins-pipeline/] or GitHub Actions [https://nemerosa.ghost.io/2022/01/17/github-actions-workflows-in-ontrack/], Ontrack will collect information like validations and promotions for each of your builds, for all

Configuration as code of Okta in Ontrack in Kubernetes

In a previous post [https://nemerosa.ghost.io/2022/01/31/installing-ontrack-with-helm/], we've seen how easy it was to install Ontrack into a Kubernetes cluster, with or without a managed database [https://nemerosa.ghost.io/2022/02/04/ontrack-deployment-kubernetes/]. In this present article,

Ontrack deployment in a Digital Ocean Kubernetes cluster

It's fairly easy to deploy Ontrack using Helm [https://nemerosa.ghost.io/2022/01/31/installing-ontrack-with-helm/]. However, while his may suitable for a demo or a test, for production, it might be better to use a managed database instead of pod running Postgres. The Ontrack

Installing Ontrack with Helm

Ontrack provides many ways for it to be installed [https://static.nemerosa.net/ontrack/release/latest/docs/doc/index.html#installation] : Docker, RPM/Debian, JAR, etc. You can also use Helm to deploy it on a Kubernetes cluster. It's as simple as running: helm repo add ontrack https:

ontrack

Auto ingestion of GitHub Actions workflows in Ontrack

Starting with Ontrack 4.1, you can configure your GitHub organizations and repositories to automatically send GitHub Actions workflows events to Ontrack, in order to record the activity of all your pipelines. In a first part, this article will explain how to configure GitHub & Ontrack. The second part will

ontrack

Ontrack for Jenkins pipelines

Ontrack [http://nemerosa.github.io/ontrack/] collects data about everything which happens in your CI/CD ecosystem. Such collection of data starts usually with your CI engine. Ontrack itself is agnostic when it comes to the CI engine but this article will focus on getting you started, step by step,

ontrack

Setting up Ontrack with Jenkins

Ontrack [http://nemerosa.github.io/ontrack/] collects data about everything which happens in your CI/CD ecosystem. Such collection of data starts usually with your CI engine. Ontrack itself is agnostic when it comes to the CI engine but this article will focus on getting you started, step by step,

ontrack

Ontrack V4

Ontrack [https://nemerosa.github.io/ontrack/] evolves, together with the CI/CD landscape, and it was time for a new major version, bringing changes which make it more versatile and flexible to deal with the amount of data that your pipelines create hour after hour, minute after minute. Ontrack V4

Ontrack 3.41

Ontrack 3. [https://github.com/nemerosa/ontrack/releases/tag/3.38.0]41 release is now available and this is a big one. First of all, it's never been so easy to get started with Ontrack. Just make sure you have Docker Compose available and run: curl -fsSLO

Ontrack 3.38

I have been quite lazy for the last releases of Ontrack and I'll try to be more consistent for the next ones. Ontrack 3.38 [https://github.com/nemerosa/ontrack/releases/tag/3.38.0] is now released. Project labels Projects can now be associated with labels, which

Ontrack 2.35 / 3.35

Ontrack 2.35 [https://github.com/nemerosa/ontrack/releases/tag/2.35.0] and 3.35 [https://github.com/nemerosa/ontrack/releases/tag/3.35.0] are now released. Those releases bring numerous fixes and new features. Feature: run info That's a feature which was really overdue - the

ontrack

Ontrack 2.30 ... and 3.0

Ontrack 2.30 [https://github.com/nemerosa/ontrack/releases/tag/2.30.0] is now released... and the version 3 is finally out of beta. Validation stamp filters You can define, manage and use validation stamp filters [http://nemerosa.github.io/ontrack/release/2.30.0/doc/index.html#branches-

Ontrack 2.29

Ontrack 2.29 [https://github.com/nemerosa/ontrack/releases/tag/2.29.0] is now released. GraphQL support The big change in Ontrack 2.29 is the introduction of the GraphQL [http://graphql.org/] support. Most of the Ontrack model, including some core extensions, is exposed through the GraphQL end

Ontrack 2.28

Ontrack 2.28 [https://github.com/nemerosa/ontrack/releases/tag/2.28.0] is now released. Support for GitLab Starting from version 2.28.0, Ontrack now supports GitLab [https://about.gitlab.com/]. You can create a global configuration for the connection to a GitLab instance and then configure the

Creating a Docker Swarm at DigitalOcean using Terraform

Since version 1.12 of Docker [https://www.docker.com/], it has become fairly easy to create a Docker Swarm. While many excellent blog articles [https://technologyconversations.com/2016/07/29/docker-swarm-introduction-tour-around-docker-1-12-series/] deal very well with using the Swarm, they usually create

continuous__delivery

Docker in Docker in Jenkins pipeline

I had a simple case: * a build which creates some database Docker container so that integration tests can run against it - using Docker Compose for example * I want to run the build in a Docker container so that my build environment can be defined using a Dockerfile stored together with

Ontrack 2.24

Ontrack 2.24 [https://github.com/nemerosa/ontrack/releases/tag/2.24.3] is now released. Simpler and faster home page The home page loads faster, especially when there is a lot of projects. Only projects you select as favourites will have their full details being displayed: To select a

Ontrack 2.22

Ontrack 2.22 [https://github.com/nemerosa/ontrack/releases/tag/2.22.0] is now released. Authentication changes Starting from version 2.22, Ontrack will now start by default with project view granted to all. > To enable authentication, log as administrator (default user name / password is admin / admin), go

Saving money with Jenkins, Digital Ocean and Docker

Once upon a time, I was using Jenkins [https://jenkins.io/] to build my applications on a lonely but powerful master instance, hosted at Digital Ocean [https://www.digitalocean.com/]. Everything was good until I realized I paid 40 USD a month for a machine which was idle most of