Thomas Haller 763cb8d486 ci: use common script for tests on travis and gitlab ... For one, it's not unreasonable that we want to run the same tests both for gitlab and travis. Move the actual tests into a script, which is called by both CI environments. We still can do something different, based on the environment. The advantage here is, that the common part will be shared, and the places where we differ can easily be spot. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/44		2018-11-12 11:29:37 +01:00
..
checkpatch-feature-branch.sh	checkpatch: quote variable in "checkpatch-feature-branch.sh"	2018-10-22 18:21:41 +02:00
checkpatch.pl	checkpatch: complain about XXX markers in code	2018-10-25 11:20:10 +02:00
nm-ci-run.sh	ci: use common script for tests on travis and gitlab	2018-11-12 11:29:37 +01:00
nm-import-openconnect	contrib/scripts: nm-import-openconnect - script for importing OpenConnect VPN configs to NM	2015-05-19 09:21:50 +02:00
nm-import-openvpn	all: drop trailing spaces	2018-02-07 13:32:04 +01:00
nm-import-vpnc	contrib/scripts: nm-import-vpnc - script for importing Cisco VPN configs to NM	2015-05-19 09:21:50 +02:00
NM-log	contrib: adjust NM-log for changes to platform logging	2018-10-23 12:03:59 +02:00
test-macsec	contrib: add macsec test script	2017-01-16 17:47:10 +01:00