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.

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

BuildbotServiceManager: support reconfiguration for legacy services #2605

Merged
merged 3 commits into from Jan 24, 2017

Conversation

tardyp
Copy link
Member

@tardyp tardyp commented Jan 16, 2017

We have a lot of legacy services (Schedulers and ChangeSources)
which do not support reconfigService, and are not reconfigurable.

Porting everything to reconfigurable is a lot of work, mainly in the unit tests
as they must properly construct a service hierarchy.

Rewritting everything makes few sense, so we add a method so that the
BuildbotServiceManager detects when the service do not support reconfiguration
and then just swap the old service with the new service, instead of reconfigure.
This is racy and not optimal, but much better than not reconfiguring (without warning).

Contributor Checklist:

  • I have updated the unit tests
  • [ x I have created a file in the master/buildbot/newsfragment directory (and read the README.txt in that directory)
  • I have updated the appropriate documentation

We have a lot of legacy services (Schedulers and ChangeSources)
which do not support reconfigService, and are not reconfigurable.

Porting everything to reconfigurable is a lot of work, mainly in the unit tests
as they must properly construct a service hierarchy.

Rewritting everything makes few sense, so we add a method so that the
BuildbotServiceManager detects when the service do not support reconfiguration
and then just swap the old service with the new service, instead of reconfigure.
This is racy and not optimal, but much better than not reconfiguring (without warning).

Signed-off-by: Pierre Tardy <tardyp@gmail.com>
@mention-bot
Copy link

@tardyp, thanks for your PR! By analyzing the history of the files in this pull request, we identified @djmitche, @warner and @rodrigc to be potential reviewers.

@tardyp tardyp force-pushed the changesources branch 2 times, most recently from 325c465 to 7c38da9 Compare January 24, 2017 09:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants