feat(tasks) Simplify taskworker rollout options & update devservices/server#96966
Closed
feat(tasks) Simplify taskworker rollout options & update devservices/server#96966
Conversation
…server With the rollout of taskworkers complete in saas, we can simplify the rollout option and enable taskworkers by default in local development. I'm going to disable this option for the August self-hosted release and enable it for the September relase once docs have been published. I've also updated the devservices mode configuration and devserver options to prefer taskworker but left escape hatches for running celery if required. Refs getsentry/taskbroker#453
markstory
added a commit
to getsentry/self-hosted
that referenced
this pull request
Aug 1, 2025
Disable taskworkers for self-hosted until the documentation has been published. Refs getsentry/sentry#96966
❌ 32 Tests Failed:
View the top 3 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
BurstRunner will require some rework to make it compatible with Taskworker dispatching.
Member
Author
|
Converting to a draft as I'm going to need to break this down more. |
aldy505
pushed a commit
to getsentry/self-hosted
that referenced
this pull request
Aug 4, 2025
Disable taskworkers for self-hosted until the documentation has been published. Refs getsentry/sentry#96966
Contributor
|
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you remove the label "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
Member
Author
|
Closing as this is a bit of a mess now. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
With the rollout of taskworkers complete in saas, we can simplify the rollout option and enable taskworkers by default in local development. I'm going to disable this option for the August self-hosted release and enable it for the September relase once docs have been published.
I've also updated the devservices mode configuration and devserver options to prefer taskworker but left escape hatches for running celery if required.
Refs getsentry/taskbroker#453