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

Give an example test file for /etc/buildbot/settings.yaml #301

Open
emmatyping opened this issue Jan 20, 2022 · 3 comments
Open

Give an example test file for /etc/buildbot/settings.yaml #301

emmatyping opened this issue Jan 20, 2022 · 3 comments

Comments

@emmatyping
Copy link
Contributor

emmatyping commented Jan 20, 2022

Hi! I am planning on adding support for cross compiling and then Emscripten as a platform. However I am unsure how to set up a realistic testing environment.

I can run the current master code, but it seems that the buildbot master relies on a file /etc/buildbot/settings.yaml to configure workers.

I am unsure of what the format of the file should be for testing. Could you give an example of what this file should look like please? (I can guess some of the information from settings.py, but I don't know what the configuration looks like for workers)

@pablogsal
Copy link
Member

Hi @ethanhs,

I can try to give you a sample later today but in theory, you don't need it for what you want. You may be able to just configure a local worker:

https://docs.buildbot.net/latest/manual/configuration/workers.html#local-workers

You can modify locally this:

WORKERS = get_workers(settings)

To point only to your local worker. It has been a while since I did that in the past so I am sure they may be some gotchas but that's how I have iterated in the past when doing modifications to the worker workflow or plugins.

@zware
Copy link
Member

zware commented Jan 20, 2022

First off, we should probably adjust

settings_path = os.path.join('/etc', 'buildbot', 'settings.yaml')
to check a PYBUILDBOT_SETTINGS_PATH environment variable for a replacement path so you don't have to stick a local test config file in /etc/buildbot. From there, your test settings file could just be use_local_worker: true to use the single local worker, and you can add anything else you need as you find you need it :). The only worker configuration you might need would be something like:

workers:
    smith-emscripten:
        password: somepassword

@emmatyping
Copy link
Contributor Author

Ok, thank you! I will try that out. I do think having a configurable path with an example would be good, because it would prevent mistakes like committing temporary changes to master.cfg.

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

No branches or pull requests

3 participants