-
Notifications
You must be signed in to change notification settings - Fork 19
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
New include_java_xrs config option; systemd init scripts now use --ex…
…ec option
- Loading branch information
Showing
18 changed files
with
161 additions
and
78 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,53 +1,65 @@ | ||
Stork by Fizzed | ||
=============== | ||
|
||
## Overview | ||
|
||
Stork heavily interacts with various operating systems. While many unit tests | ||
are designed to run locally (and not in a virtual machine), to truly do development | ||
with Stork you'll want to verify what you changed works across a number of | ||
operating systems. | ||
|
||
## Vagrant | ||
|
||
Make sure you have at least Vagrant v1.9.8 installed as well as the extension pack. | ||
You can verify your version by running: | ||
|
||
vagrant -v | ||
|
||
Stork interacts with various operating systems. While many unit tests are designed | ||
to run locally (and not in a virtual machine), the rest of them require 1 or | ||
more virtual machines to run. Vagrant is used to help setup virtual machines running | ||
various operating systems so we can run unit tests against them. The unit tests | ||
are designed to detect what's virtual machines are running and then run tests | ||
against them -- so you only need to spin up what you'd like to test against. | ||
Let's run thru an "ubuntu14" example: | ||
Vagrant is used to help setup virtual machines running various operating systems | ||
so we can run unit tests against them. The unit tests are designed to detect what's | ||
virtual machines are running and then run tests against them -- so you only need to | ||
spin up what you'd like to test against. Let's run thru an "ubuntu14" example: | ||
|
||
To spin up an Ubuntu 14.04 virtual machine: | ||
|
||
vagrant up ubuntu14 | ||
|
||
To run unit tests against a specific virtual machine: | ||
## Running Unit Tests | ||
|
||
To run all unit tests against a specific virtual machine: | ||
|
||
mvn test -Dhost=ubuntu14 | ||
|
||
To run just the launchers test: | ||
To test only the stork-launcher module on that host: | ||
|
||
mvn -am -pl stork-launcher test -DfailIfNoTests=false -Dtest=com.fizzed.stork.launcher.*Test -Dhost=ubuntu14 | ||
|
||
To test only the stork-deploy module on that host: | ||
|
||
mvn -am -pl stork-launcher-test test-compile test -Dhost=ubuntu14 -DfailIfNoTests=false -Dtest=com.fizzed.stork.test.LauncherTest | ||
mvn -am -pl stork-deploy test -DfailIfNoTests=false -Dtest=com.fizzed.stork.deploy.*Test -Dhost=ubuntu14 | ||
|
||
To run your tests locally, just use the host of `local`: | ||
|
||
mvn test -Dhost=local | ||
|
||
## Testing for Windows on Linux/Mac | ||
|
||
To run tests against Windows (if on Linux or OSX): | ||
|
||
vagrant up windows10 | ||
|
||
Be patient as the image is ~6GB to download. Once ready, you'll need to make | ||
sure Java 8 is on it. Open up VirtualBox, double click the vm, then open powershell | ||
sure Java 8 is on it. We didn't have time to make the vagrant install do all | ||
the prep, so there's a couple manual steps. Open up VirtualBox, double click | ||
the vm, then open powershell: | ||
|
||
choco install -y jdk8 | ||
|
||
Then run your tests | ||
Then you can run any of the tests above against the host `windows10`: | ||
|
||
mvn test -Dhost=windows10 | ||
|
||
If you change how the launchers work, please look at creating a unit test for | ||
them in `stork-launcher-test`. Validating your change doesn't break across | ||
numerous operating systems is important. | ||
|
||
## Windows | ||
|
||
Its incredibly important your windows scripts have correct line endings or | ||
NOTE: its incredibly important your windows scripts have correct line endings or | ||
the Windows cmd.exe interpreter will give you strange results. | ||
|
||
unix2dos stork-launcher/src/main/resources/com/fizzed/stork/launcher/windows/* | ||
unix2dos stork-launcher/src/main/resources/com/fizzed/stork/launcher/windows/* |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.