Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #354
Currently, when the site's master branch is updated, a Travis build installs the dependencies and runs the tests for each of the
finished
tutorial demos. This causes deployment times to be excessively long and ties up CI resources.This change addresses this issue by introducing a
precommit
task to the grunt configuration that allows all of the demos to be inspected for changes and runs the tests if they have been. Upon successful completion, a hash is stored containing the signature of the demo code. This is then checked by Travis and, if the calculated hash matches the stored one, the tests are not re-run.In addition to creating the new grunt task, this change also updates the .travis.yml script to remove that parts that were triggering the tests previously. This has been replaced by the addition of a
verifyTutorials:ci
task in the grunt configuration. This change makes it easier to determine if a demo needs to be rebuilt by reusing code from theprecommit
task to calculate the demo's hash and comparing it to the one that was stored.