-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[content-service] Revert #11895 #13549
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
Conversation
started the job as gitpod-build-aledbf-defgit.1 because the annotations in the pull request description changed |
/werft run with-clean-slate-deployment 👍 started the job as gitpod-build-aledbf-defgit.4 |
/werft run with-clean-slate-deployment 👍 started the job as gitpod-build-aledbf-defgit.5 |
/werft run with-integration-tests=workspace 👍 started the job as gitpod-build-aledbf-defgit.6 |
/werft run with-integration-tests=workspace 👍 started the job as gitpod-build-aledbf-defgit.8 |
/werft run with-integration-tests=workspace 👍 started the job as gitpod-build-aledbf-defgit.10 |
/werft run with-clean-slate-deployment 👍 started the job as gitpod-build-aledbf-defgit.12 |
test/tests/components/ws-manager/additional_repositories_test.go
Outdated
Show resolved
Hide resolved
/werft run with-integration-tests=workspace 👍 started the job as gitpod-build-aledbf-defgit.14 |
63f631d
to
0d0e281
Compare
/werft run 👍 started the job as gitpod-build-aledbf-defgit.18 |
/werft run with-integration-tests=workspace 👍 started the job as gitpod-build-aledbf-defgit.19 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code LGTM. But it would be good if we could enhance the integration test to check the workspace pod branch name is as expected.
/hold
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Cloning multi-repos on branches now works again as advertised.
/werft run 👍 started the job as gitpod-build-aledbf-defgit.20 |
Check the branch is the expected
/werft run with-integration-tests=workspace with-large-vm with-clean-slate-deployment 👍 started the job as gitpod-build-aledbf-defgit.22 |
/hold as it's blocking the merge queue |
/werft run with-integration-tests=workspace with-large-vm with-clean-slate-deployment 👍 started the job as gitpod-build-aledbf-defgit.23 |
started the job as gitpod-build-aledbf-defgit.24 because the annotations in the pull request description changed |
started the job as gitpod-build-aledbf-defgit.25 because the annotations in the pull request description changed |
Description
When we open a workspace from a branch and the repository contains a .gitpod.yml file with
additionalRepositories
, we should not assume the branch exists in those repositories. Also, when we specify a branch in one of theadditionalRepositories
, we should be able to use that branch.Related Issue(s)
Fixes #13527
Fixes #13512
Reverts #11895
How to test
Release Notes
Werft options:
If enabled this will build
install/preview
Valid options are
all
,workspace
,webapp
,ide