Experimental automated testing of Autodesk Forge services using Travis CI.
| Branch | Status |
|---|---|
| master |  |
| tests/rvt |  |
| tests/iam |  |
| tests/dwfx |  |
| tests/nwd |  |
Note: most of the following actions can only be taken by collaborators of this github repo. If you're not a collaborator yet, ask the admin of this repo to be invited.
Go to https://travis-ci.org/petrbroz/forge-continuous-testing, and choose the Trigger build option in the More options menu:
Find the branch you want to test, and start the test using the Trigger custom build button.
Currently we're testing different types of file formats in their own branches (so that they can run as separate builds/jobs in Travis). For example, the tests/rvt branch configures a couple of sample Revit models in the .travis.yml config file.
Go to https://travis-ci.org/petrbroz/forge-continuous-testing/builds, and find the failing build/test. On the build page you can choose to restart the entire build using the Restart build button, or just some of the build "jobs" (representing individual sample files of the tested file format):
Follow the same steps as when manually triggering a new test, but customize the config to pass the --update flag
to the test script. Currently the only test available is tests/model-derivative/basic.js (accepting a bucket key
and an object key as its two parameters), so the modified config would look like this:
script: node tests/model-derivative/basic.js $FORGE_BUCKET_KEY $FORGE_OBJECT_KEY --update
If you want to skip a build when submitting code changes, use [skip travis] or a similar phrase in your commit message.