v5 release notes

V5 release notes

V5 content

See V5 changes.

Migration from V4

See V5 migration.

Changelog

5.0.25

In the branch links graph, there is now a button to display the changelog to the latest build when not using this one:

5.0.24

In the list of auto-versioning targets for a promotion or a promotion run, only the eligible targets are displayed by default. There is a new filter to display all targets and/or to filter them on project name.

In the CI config, you can now specify a filter based on the SCM branch name. For example:

version: v1
configuration:
  default:
    branch:
      autoVersioning:
        branchFilter:
          includes:
            - main
            - 'release\\.*'
          excludes:
            - 'release\\1\..*'

#1548 Missing filter on the branch for the AV extension in the CI config

5.0.23

In the branch links graph, when selecting a branch node, the associated links and the corresponding other branch nodes are now displayed.

In the build page, in the downstream & upstream views, you can now filter on project names.

In the promotion run page and in the promotion level page, when looking at the auto-versioning trail (where you can see the targets of auto-versioning for this promotion), you can now filter on project name and on the eligibility of the target.

In the build links graph, it's now possible to navigate to the links of another build directly from the graph.

5.0.19

#1540 In the AV audit, have an option to display the state of all displayed PRs

In several places:

• auto-versioning audit table
• auto-versioning audit details
• branch links graph
• branch links table

You can now click a "Load PR statuses" to see the state of all PRs displayed in the page.

In the "auto-versioning audit details" page, the PR status is already loaded.

Example:

5.0.18

• #1537 Wrong location of the deployment error mention

5.0.17

• #1536 Adding more information to the job history tooltip

5.0.16

• #1533 A deployment must be marked as failed (error) if one of its workflows fails

5.0.15

• #1532 Storing and displaying the history of job executions

5.0.14

• #1531 Document the metrics for the background jobs
• #1534 Missing metrics in the documentation

A new metric has been added to monitor the duration of the background jobs: ontrack_job_duration

5.0.13

• #1530 Fixed the Prometheus endpoint

5.0.12

• #1528 The search box now focuses on sections having actual results
• #1529 Indexation of commits/issues must not fail for one single repository

5.0.8

• #1524 Cannot read properties of undefined (reading 'forEach') in some very heavy dependency graphs
• #1526 Searchbox should be aligned to the left
• #1527 Searchbox optimizations

5.0.7

#1510 Alternative way of displaying state of links at branch level using a table

• When clicking on a branch link, highlighting the consumer and the dependency:

• When clicking on a branch link, highlighting the upstream and downstream dependencies:

• In the branch nodes, there is a button to restrict the graph to the selected branch node and its upstream and downstream dependencies:

• Finally, by clicking on the table button in the bottom right corner:

you can display the downstream dependencies in a table:

You can also filter the table to see only errors:

5.0.6

#1522 More details when logging a JSON parsing error for a configuration.

5.0.5

#1518 In branch dependency graphs, when not using the last build, the link node is displayed with a different color:

5.0.4

• #1517 GraphQL semantic changelog always returns issues

5.0.3

Semantic changelogs based on conventional commits are now supported.

See the documentation for more information.

5.0.2

The Jenkins pipeline library step ontrackCliAutoVersioning has been adapted in its last version to use the same configuration properties as for the CLI, the CI config, etc. Old property names are still supported for backward compatibility but will be removed in a future version (V6).

In order for these old property names to work, your Yontrack version must be at least 5.0.2.

In any case, while ontrackCliAutoVersioning will keep being supported, we encourage its replacement by the new ontrackCliCiConfig step.

5.0.1

A single auto-versioning configuration can now be disabled using the disabled flag. For example:

autoVersioning:
  configurations:
    - sourceProject: ontrack
      sourceBranch: main
      sourcePromotion: RELEASE
      # ...
      disabled: true

Of course, if not provided, its default value is false.