Skip to content

[dev] Set usage reconciliation schedule to 1m in preview #11580

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

Merged
merged 1 commit into from
Jul 23, 2022

Conversation

andrew-farries
Copy link
Contributor

@andrew-farries andrew-farries commented Jul 22, 2022

Description

Run usage reconciliation more frequently in preview envs to make developing the service easier.

Previously to trigger usage runs in preview it was necessary to edit the configmap.

Related Issue(s)

Part of #9036

How to test

Release Notes

NONE

Documentation

Werft options:

  • /werft with-preview

@werft-gitpod-dev-com
Copy link

started the job as gitpod-build-af-configure-usage-interval.1 because the annotations in the pull request description changed
(with .werft/ from main)

Copy link
Member

@geropl geropl left a comment

Choose a reason for hiding this comment

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

Thank you! 👍

@easyCZ
Copy link
Member

easyCZ commented Jul 22, 2022

/werft run

👍 started the job as gitpod-build-af-configure-usage-interval.2
(with .werft/ from main)

@aledbf
Copy link
Member

aledbf commented Jul 23, 2022

/hold

(to allow merge of PRs)

Run usage reconciliation more frequently in preview envs to make
developing the service easier.
@andrew-farries andrew-farries force-pushed the af/configure-usage-interval branch from 1eb9d5a to 9246bd3 Compare July 23, 2022 18:42
@andrew-farries
Copy link
Contributor Author

/unhold

@roboquat roboquat merged commit 864214b into main Jul 23, 2022
@roboquat roboquat deleted the af/configure-usage-interval branch July 23, 2022 21:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants