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

Add test to check Buildbot master config #307

Merged
merged 3 commits into from Apr 7, 2016

Commits on Apr 6, 2016

  1. Refactor buildbot states

    Split the master and slave states into separate directories,
    use the standard files/ directory, and use more Jinja templating.
    aneeshusa committed Apr 6, 2016
  2. Don't autorestart Buildbot master

    Automatically restarting Buildbot when there are outstanding builds causes them
    to get lost and is generally a bad idea. Until we have a more robust way to
    restart the Buildbot master on configuration change, disable the auto-restart
    behavior.
    aneeshusa committed Apr 6, 2016

Commits on Apr 7, 2016

  1. Add test to check Buildbot master config

    This test can be run via `./test.py sls.buildbot.master`. It will only
    work properly once the Buildbot master states have been run, and is
    meant to be run either in Vagrant or on Travis, not locally.
    
    Running `./test.py` without arguments will only run the linting tests, since
    those can be run anywhere with just the source code.
    
    For now, hard-code this test to be run on the servo-master1 node on Travis.
    This should be replaced with a more intelligent test dispatcher in `test.py`
    which uses the top file via Salt's state.show_top in the future, but hard
    coding this for now will reduce Buildbot's fragility.
    aneeshusa committed Apr 7, 2016
You can’t perform that action at this time.