[JENKINS-59071] Git should include an option to "checkout the revision at build-time"

Currently the git-plugin can checkout the current head, or a specific commit, what I'm missing is an option to checkout the head at the time where the build has started.

Reason: if you have a pipeline build that was triggered at a certain time, and the devlopers checked in something before the checkout takes place these changes are picked up even if the build is already running for a while.

For example I have a pipeline that builds different repositories together one after the other. It now can happen that a build starts, checkout the first repository, then checkout the second but picks up changes commited at a later point at time (and fail because changes from the first repository are not taken into account).

The same happens if you replay a certain pipeline build, it always fetches the ltest changes and not the changes that where current at the time of the build (so replay is more a "rebuild with different script" because the build is not really replayed.

Originally reported by laeubi, imported from: Git should include an option to "checkout the revision at build-time"

• status: Open
• priority: Minor
• component(s): git-plugin
• resolution: Unresolved
• votes: 0
• watchers: 5
• imported: 2025-12-02

Raw content of original issue

Currently the git-plugin can checkout the current head, or a specific commit, what I'm missing is an option to checkout the head at the time where the build has started.

Reason: if you have a pipeline build that was triggered at a certain time, and the devlopers checked in something before the checkout takes place these changes are picked up even if the build is already running for a while.

For example I have a pipeline that builds different repositories together one after the other. It now can happen that a build starts, checkout the first repository, then checkout the second but picks up changes commited at a later point at time (and fail because changes from the first repository are not taken into account).

The same happens if you replay a certain pipeline build, it always fetches the ltest changes and not the changes that where current at the time of the build (so replay is more a "rebuild with different script" because the build is not really replayed.

The issue names the git-plugin and Jenkins pipeline checkout behavior but no files or tests. Start by locating the checkout option and pipeline entry points, then determine how a build-time revision should be selected; done means an option preserves the repository state from build start, including sequential checkouts and replayed builds.