-
Notifications
You must be signed in to change notification settings - Fork 1.3k
werft/job-config: Make previews from 20+ character branches possible #8403
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
werft/job-config: Make previews from 20+ character branches possible #8403
Conversation
Signed-off-by: ArthurSens <[email protected]>
Signed-off-by: ArthurSens <[email protected]>
pinging @gitpod-io/platform to talk about what is mentioned in the PR description |
Codecov Report
@@ Coverage Diff @@
## main #8403 +/- ##
==========================================
- Coverage 14.53% 11.17% -3.36%
==========================================
Files 51 18 -33
Lines 4872 993 -3879
==========================================
- Hits 708 111 -597
+ Misses 4102 880 -3222
+ Partials 62 2 -60
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
This would break SSH access to preview environments as we use the branch name also in other places and we assume that the branchname is the same as the destname at multiple places.
|
Good catch! I've also just noticed that you've opened #8316 (platform was not set as reviewers), I'm wondering our best option here is to just merge that one and work to get Harvester done ASAP |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@ArthurSens I believe we can close this in favour of #8692 now :) |
Yep :) |
Signed-off-by: ArthurSens [email protected]
Description
This PR effectively makes it possible to create preview environments from super long branch names by cutting it into 20 characters max. The reasons why we can't use more than 20 characters are listed here.
I'm opening this as a draft because:
The initial idea of adding a label does not work out-of-the-box as we expected.
/
, which are commonly used by our branch namesCreating this PR to start the discussion, should we give up on verifying a possible conflicting namespace? Should we go with a mixture of branch name + hash?
Related Issue(s)
Fixes https://github.com/gitpod-io/ops/issues/1252
How to test
Create a super long branch(from this PR) and create a new preview
Release Notes