Difference between revisions of "Autobuild/Integration"
Brad Linden (talk | contribs) (initial draft of testing procedures) |
m (Text replacement - "hg.secondlife.com" to "bitbucket.org/lindenlab") |
||
| Line 7: | Line 7: | ||
=== Unit Tests === | === Unit Tests === | ||
Tests are under [http:// | Tests are under [http://bitbucket.org/lindenlab/autobuild/src/tip/autobuild/tests/ autobuild/tests] | ||
You can run them by running <tt>nosetests -v</tt> from the top of the autobuild source tree. (see [http://somethingaboutorange.com/mrl/projects/nose/1.0.0/ nose documentation]) | You can run them by running <tt>nosetests -v</tt> from the top of the autobuild source tree. (see [http://somethingaboutorange.com/mrl/projects/nose/1.0.0/ nose documentation]) | ||
=== Integration Tests === | === Integration Tests === | ||
We have teamcity running a test build against a staging repo: [http://bitbucket.org/brad_linden/autobuild-integration autobuild-integration]. So changes should be pushed there first for testing before getting promoted to http:// | We have teamcity running a test build against a staging repo: [http://bitbucket.org/brad_linden/autobuild-integration autobuild-integration]. So changes should be pushed there first for testing before getting promoted to http://bitbucket.org/lindenlab/autobuild . | ||
You need to check out 4 repos side-by-side to run the tests here: | You need to check out 4 repos side-by-side to run the tests here: | ||
*[http:// | *[http://bitbucket.org/lindenlab/buildscripts buildscripts] (note this is currently broken, as default-autobuild.sh is missing for now) | ||
*autobuild (cloned from your branch with your new changes to test) | *autobuild (cloned from your branch with your new changes to test) | ||
*[http://bitbucket.org/brad_linden/autobuild-testscript autobuild-testscript] | *[http://bitbucket.org/brad_linden/autobuild-testscript autobuild-testscript] | ||
Latest revision as of 09:13, 1 May 2015
This page describes how to make changes to Autobuild and get it tested and integrated for others to use. It's intended to be analogous to the process described at How To Submit A Viewer Change but somewhat simplified.
Testing Requirements
Unit Tests
Tests are under autobuild/tests You can run them by running nosetests -v from the top of the autobuild source tree. (see nose documentation)
Integration Tests
We have teamcity running a test build against a staging repo: autobuild-integration. So changes should be pushed there first for testing before getting promoted to http://bitbucket.org/lindenlab/autobuild .
You need to check out 4 repos side-by-side to run the tests here:
- buildscripts (note this is currently broken, as default-autobuild.sh is missing for now)
- autobuild (cloned from your branch with your new changes to test)
- autobuild-testscript
- 3p-curl
Then run autobuild-testscript/build.sh. You can also test against additional packages by checking them out alongside 3p-curl and setting the test_pkgs environment variable either manually or in autobuild-testscript/BuildParams