The CLI has moved from nemerosa/ontrack-cli to yontrack/yontrack-cli. This repository should follow.
Work
These references are textual rather than resolved at runtime, so nothing is broken today — the transfer left a 301 at the old path. But that redirect is load-bearing across the whole CLI ecosystem, and nothing must ever be created at nemerosa/ontrack-cli or it disappears.
Ordering — learned the hard way on the CLI move
This repo has its own Yontrack project (ontrack-github-actions-cli-validation, id 23), and its project name is derived server-side from GITHUB_REPOSITORY. Rename the Yontrack project and repoint its GitHub property before transferring, otherwise the first post-transfer build auto-creates a second, empty project and orphans the existing build and promotion history.
Set the new repository name in GitHub's transfer dialog itself rather than transferring and then renaming, to avoid a second redirect hop.
Related
The CLI has moved from
nemerosa/ontrack-clitoyontrack/yontrack-cli. This repository should follow.Work
yontrackorganisationThese references are textual rather than resolved at runtime, so nothing is broken today — the transfer left a 301 at the old path. But that redirect is load-bearing across the whole CLI ecosystem, and nothing must ever be created at
nemerosa/ontrack-clior it disappears.Ordering — learned the hard way on the CLI move
This repo has its own Yontrack project (
ontrack-github-actions-cli-validation, id 23), and its project name is derived server-side fromGITHUB_REPOSITORY. Rename the Yontrack project and repoint its GitHub property before transferring, otherwise the first post-transfer build auto-creates a second, empty project and orphans the existing build and promotion history.Set the new repository name in GitHub's transfer dialog itself rather than transferring and then renaming, to avoid a second redirect hop.
Related