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.

Sign up for GitHub

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

Jump to bottom

Remove config for cpu bucket limiting in preview environments #11560

Merged
merged 1 commit into from
Jul 22, 2022
Merged

Remove config for cpu bucket limiting in preview environments #11560

merged 1 commit into from
Jul 22, 2022

Conversation

Furisto
Copy link
Member

@Furisto Furisto commented Jul 22, 2022 •
edited

Description

This configuration is not used anymore and will completely go away with #11374

Related Issue(s)

Fixes ##11374

How to test

  • Workspace components still work

Release Notes

None

Werft options:

  • /werft with-preview

@Furisto Furisto marked this pull request as ready for review July 22, 2022 09:10
@Furisto Furisto marked this pull request as draft July 22, 2022 09:13
@Furisto Furisto marked this pull request as ready for review July 22, 2022 09:25
liam-j-bennett
liam-j-bennett approved these changes Jul 22, 2022
View reviewed changes
Copy link
Contributor

@liam-j-bennett liam-j-bennett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛹

@roboquat roboquat merged commit 788b7b5 into main Jul 22, 2022
@roboquat roboquat deleted the fo/bucket-limiting branch July 22, 2022 15:56
@Furisto Furisto mentioned this pull request Jul 22, 2022
Merged
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@liam-j-bennett liam-j-bennett liam-j-bennett approved these changes

Assignees
No one assigned
Labels
feature: workspace classes release-note-none size/S
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@Furisto @liam-j-bennett @roboquat