Changes between Version 36 and Version 37 of OpenVPN_QA
- Timestamp:
- 02/28/18 09:26:08 (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
OpenVPN_QA
v36 v37 10 10 11 11 ||Tool/process ||Automated ||In use ||Scope ||Extra requirements ||B.patch||B.merge||A.merge||B.release||B.distro merge|| 12 ||"make check" ||No[5] ||Yes ||Build ||None ||X || || || || || 13 ||vagrant ||No ||Yes ||Build,integration ||Vagrant installed ||X || || || || || 12 ||"make check" ||No![5] ||Yes ||Build ||None ||X || || || || || 13 ||vagrant (build) ||No![6] ||Yes ||Build ||Vagrant installed ||X || || || || || 14 ||vagrant (server) ||No![7] ||Needs work ||Integration ||Vagrant installed ||X || || || || || 14 15 ||unit tests ||Yes ||Needs work ||Regression ||Cmocka installed ||X || || || || || 15 16 ||code review ||No ||Yes ||Everything ||None || ||X || || || || … … 23 24 ||win testsuite![2]||No![4] ||Yes ||Integration ||Windows || ||(X)![3]||(X)![3]||X || || 24 25 ||linux packages ||No![4] ||Yes ||Everything ||Debian OS || ||(X)![3]||(X)![3]||(X)![3] ||X || 26 ||distro qa![8] ||- ||- ||- ||None || || || || || || 25 27 26 28 Most OpenVPN subprojects, including [https://github.com/OpenVPN/openvpn openvpn], [https://github.com/OpenVPN/openvpn-build openvpn-build], [https://github.com/OpenVPN/openvpn-gui openvpn-gui] and [https://github.com/OpenVPN/tap-windows6 tap-windows6] now have Travis CI and/or !AppVeyor support. … … 33 35 1. Could be automated, but requires a fair amount of work; integration with Windows snapshots could be accomplished with [https://chocolatey.org/ Chocolatey]. 34 36 1. "make check" as such does not run automatically at build. However, some of the other CI tools (travis, buildbot) do run it on every commit. 37 1. Vagrant VMs allow any developer - core or otherwise - to test OpenVPN on any esoteric platform before sending a patch. The process is manual right now. 38 1. OpenVPN servers provided as Vagrant VMs can be used to launch client connectivity tests against OpenVPN servers configured in various ways. This is akin to what Buildbot does at the moment, but the process is/will be more manual and oriented towards single developers. 39 1. The "Distro QA" line is here to emphasize the fact that downstread distributors of OpenVPN have their own QA processes in place. A large part of OpenVPN downloads come through these distributors, so we indirectly benefit from their QA also. 35 40 36 41 Key: