Compare: Buildbot administration
Unified
Split
Showing
with
72 additions
and 25 deletions.
- +1 −1 Adding-a-repo-to-Homu.md
- +8 −0 Bots.md
- +1 −1 Buildbot-administration.md
- +14 −1 Building-for-Android.md
- +3 −1 Github-challenges.md
- +5 −5 Governance.md
- +2 −1 Infrastructure.md
- +9 −0 Profiling.md
- +14 −13 Roadmap.md
- +8 −0 SaltStack-Administration.md
- +1 −0 Tag-label-names-and-definitions.md
- +6 −2 Testing.md
| @@ -61,7 +61,7 @@ $ cd servo-saltfs | ||
| $ git checkout -b new-feature | ||
| ``` | ||
|
|
||
| Make changes as needed, and test them using [Vagrant](https://vagrantup.com), version 1.8 or better (Ubuntu may still have 1.7.x). A Vagrantfile is included in the [servo/saltfs](https://github.com/servo/saltfs/) repo. Each node type has a corresponding Vagrant target, and Vagrant will run the Salt states when provisioning. For example, you might run these commands from within your checkout of the saltfs repo (same directory as the Vagrantfile): | ||
| Make changes as needed, and test them using [Vagrant](https://vagrantup.com); a Vagrantfile is included in the [servo/saltfs](https://github.com/servo/saltfs/) repo. Vagrant's Salt provisioner tends to make backwards-incompatible changes fairly often, so only a few versions of Vagrant will work; the Vagrantfile has information about which ones. Currently, version 1.8.1 is recommended (note that many OSs like Ubuntu may still have older versions like 1.7.x, so you may need to [download a different version](https://releases.hashicorp.com/vagrant/)). Each node type has a corresponding Vagrant target, and Vagrant will run the Salt states when provisioning. For example, you might run these commands from within your checkout of the saltfs repo (same directory as the Vagrantfile): | ||
|
|
||
| ```console | ||
| $ vagrant up # start all VMs configured in Vagrantfile, alternately `vagrant up servo-master1` to start just one | ||