ontrack - Nemerosa

ontrack

A collection of 5 posts

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 detail

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,

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 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 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-validation-stamp-filters]