70 | | OpenVPN project's buildslaves run connectivity tests against several OpenVPN test servers once per on every commit. For these tests to work you need to run buildbot as ''root''. You will also need test certificates and a ''t_client.rc'' config file from buildmaster admins. Once you've have the files, put them to ''/home/buildbot'' and make sure they are readable by root. After this the admins will force a build on your buildslave and then send you a fixed ''t_client.rc'' file to replace the generic one you received earlier. |
| 70 | OpenVPN project's buildslaves run connectivity tests against several OpenVPN test servers once per on every commit. For these tests to work you need to run buildbot as ''root''. |
| 71 | |
| 72 | As the tests connect to remote OpenVPN servers you will need test certificates and a ''t_client.rc'' config file from the buildmaster admins. Once you've have the files, put them to ''/home/buildbot'': |
| 73 | |
| 74 | {{{ |
| 75 | $ tree /home/buildbot |
| 76 | /home/buildbot |
| 77 | ├── t_client.rc |
| 78 | ├── test-ca.crt |
| 79 | ├── test-client.crt |
| 80 | ├── test-client.key |
| 81 | └── test-ta.key |
| 82 | |
| 83 | 0 directories, 5 files |
| 84 | }}} |
| 85 | |
| 86 | Make sure that the files are readable by root and named exactly as shown above. |
| 87 | |
| 88 | Now the admins will force a build and the associated connectivity tests on your buildslave. The first build is expected to fail, because the t_client.rc you were given first is a generic one. Once the IPv4 and IPv6 addresses the connectivity test servers give your client are known, the admins can send you a new ''t_client.rc'' tailored for you buildslave. |