Clone Tools
  • last updated a few seconds ago
Constraints: committers
Constraints: files
Constraints: dates
Pin all remote projects to exact refs, don't use branches

Pinning to branches means the build is not fully reproducible, as changes in the remote repo can alter the outcome of this build.

  1. … 3 more files in changeset.
Build commit distribution when necessary (#7616)

This fixes and partially fixes .

In we supported running performance tests against fork point commit, now we want to make `5.1-commit-1a2b3c4d` a valid baseline version - users can specify this version in `--baselines` parameter:

- If commit baseline is set explicitly (like `5.1-commit-1a2b3c4d`), then build the corresponding commit distribution.

- Otherwise, if the current branch is not `master` or `release`, calculate the fork point commit then build the corresponding commit distribution.

This PR also publishes build scan to TeamCity build log and reuses `RemoteProject` logic and get rid of duplicate `git clone` code.

    • -0
    • +97
  1. … 7 more files in changeset.