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

Conversation

@aneeshusa
Copy link
Member

aneeshusa commented Apr 7, 2016

A few things in this PR (in separate commits):

  • Refactor the Buildbot states to standard paths, use more Jinja templating
  • Switch the Buildbot master service to not restart automatically. It will need to be restarted manually if there are configuration changes. This should alleviate the need for state.apply.
  • Use the buildbot checkconfig command to confirm the syntax of the Buildbot master configuration, and run it on Travis. This can be run via ./test.py sls.buildbot.master, but note that this won't work locally - it needs to be run in an environment where the Buildbot master states have run, i.e. Travis or Vagrant.

cc @larsbergstrom @edunham


This change is Reviewable

aneeshusa added 3 commits Apr 6, 2016
Split the master and slave states into separate directories,
use the standard files/ directory, and use more Jinja templating.
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.
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.
@edunham
Copy link
Contributor

edunham commented Apr 7, 2016

@bors-servo r+

Thank you! This looks great!

@bors-servo
Copy link
Contributor

bors-servo commented Apr 7, 2016

📌 Commit d5f50b0 has been approved by edunham

@bors-servo
Copy link
Contributor

bors-servo commented Apr 7, 2016

Testing commit d5f50b0 with merge 566c5ba...

bors-servo added a commit that referenced this pull request Apr 7, 2016
Add test to check Buildbot master config

A few things in this PR (in separate commits):
  - Refactor the Buildbot states to standard paths, use more Jinja templating
  - Switch the Buildbot master service to not restart automatically. **It will need to be restarted manually if there are configuration changes.** This should alleviate the need for `state.apply`.
  - Use the `buildbot checkconfig` command to confirm the syntax of the Buildbot master configuration, and run it on Travis. This can be run via `./test.py sls.buildbot.master`, but note that this won't work locally - it needs to be run in an environment where the Buildbot master states have run, i.e. Travis or Vagrant.

cc @larsbergstrom @edunham

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/saltfs/307)
<!-- Reviewable:end -->
@larsbergstrom
Copy link
Contributor

larsbergstrom commented Apr 7, 2016

This is awesome - great work @aneeshusa!

@bors-servo
Copy link
Contributor

bors-servo commented Apr 7, 2016

☀️ Test successful - travis

@bors-servo bors-servo merged commit d5f50b0 into servo:master Apr 7, 2016
2 checks passed
2 checks passed
continuous-integration/travis-ci/pr The Travis CI build passed
Details
homu Test successful
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

4 participants
You can’t perform that action at this time.