157 | | There are too many to list. However, the builds that use default build flags also trigger connectivity tests. |
| 157 | Each commit triggers several builds of OpenVPN, each with a different set of configure options: |
| 158 | |
| 159 | {{{ |
| 160 | config_opt_combos = [ |
| 161 | "", |
| 162 | "--disable-crypto", |
| 163 | "--disable-crypto --disable-lzo", |
| 164 | "--disable-crypto --disable-lzo --disable-management", |
| 165 | "--disable-crypto --disable-management", |
| 166 | "--disable-lz4", |
| 167 | "--disable-lzo", |
| 168 | "--disable-lzo --disable-lz4 --enable-comp-stub", |
| 169 | "--disable-lzo --disable-management", |
| 170 | "--disable-management", |
| 171 | "--disable-server --enable-small", |
| 172 | "--enable-small", |
| 173 | "--with-crypto-library=mbedtls --enable-crypto", |
| 174 | ] |
| 175 | }}} |
| 176 | Most of the builds just build OpenVPN to ensure the buildsystem works. However, two of them also trigger a suite of t_client.sh connectivity tests: |
| 177 | |
| 178 | * ./configure |
| 179 | * ./configure --with-crypto-library=mbedtls --enable-crypto |
| 180 | |
| 181 | The connectivity tests help ensure that basic functionality in OpenVPN is never completely broken. |