Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v8] Backport build features to work with teleport.e and teleport-private #12777

Merged
merged 6 commits into from
May 24, 2022

Conversation

tcsc
Copy link
Contributor

@tcsc tcsc commented May 19, 2022

Backports

  1. the use of an optional deployment key, and
  2. the ability to optionally disable the unshallowing action

...when checking out teleport

See-Also: #10506
See-Also: #12590
See-Also: #12624

tcsc added 2 commits May 20, 2022 09:24
Backports
 1. the use of an optional deployment key, and
 2. the ability to optionally disable the unshallowing action

...when checking out teleport

See-Also: #10506
See-Also: #12590
See-Also: #12624
tcsc added 2 commits May 23, 2022 13:25
GCB checks out code for testing a PR as a shallow clone. The `teleport`  build requires unshallowing the clone in order to run analytics on the change, so it runs `git fetch --unshallow` to get the whole repo.

Unfortunately, the `teleport.e` repo already has a full teleport repository when it runs the test scripts, so unshallowing fails.

This change allows the unit & integration testing scripts to optionally skip the unshallow step, so that the teleport.e build triggers can succeed.
@tcsc tcsc merged commit 17326a0 into branch/v8 May 24, 2022
@zmb3 zmb3 deleted the tcsc/branch/v8/skip-unshallow branch April 26, 2023 21:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants