the automatic update functionality is definetily missing for windows part.
I'll try chocolatey for that.

2016-11-07 22:11 GMT+05:00 Samuli Seppänen <sam...@openvpn.net>:

> Il 07/11/2016 18:56, Илья Шипицин ha scritto:
>
>>
>>
>> 2016-11-07 20:50 GMT+05:00 Samuli Seppänen <sam...@openvpn.net
>> <mailto:sam...@openvpn.net>>:
>>
>>     Il 07/11/2016 15:15, Илья Шипицин ha scritto:
>>
>>         Hello,
>>
>>         I used @mattock's powershell scripts
>>
>>         voila :)
>>
>>         https://jk.testkontur.ru/job/openvpn%20connect%20to%20jk-tes
>> t/3/console
>>         <https://jk.testkontur.ru/job/openvpn%20connect%20to%20jk-te
>> st/3/console>
>>
>>         it is strange for few reasons, but it looks very promising. we can
>>         automate a lot of testing in such way.
>>
>>
>>     Nice! At some point I wanted to implement a Powershell-based
>>     "buildslave" that could run in the background on Windows. Several
>>     people could run that "buildslave" to test latest OpenVPN Windows
>>     build against their respective OpenVPN servers.
>>
>>
>> it is not that hard to run jenkins buildslave, we use it in production.
>>
>> https://jk.testkontur.ru/job/openvpn%20connect%20to%20jk-test/4/console
>>
>>
>> it's getting better :)
>>
>
> Yeah, and I'm definitely _not_ adding Jenkins to _our_ mix right now :).
>
> Windows is special in the sense that we don't build OpenVPN on that
> platform. The cross-compile part is being tested on several levels already,
> so testing the openvpn.exe executable is the more interesting part.
>
> One way to get the latest cross-compiled Windows installers easily into
> the hands of testers would be to setup our own Chocolatey[1] repository and
> automatically push latest installers there. The said repository could be
> used by the Windows "buildslave" to automatically fetch the latest
> snapshot, install it, and to run connectivity tests using
> openvpn-windows-test powershell scripts, and to report back any failures.
>
> This would also speed up Windows release process, as the installers would
> not really need much extra testing. And we would not have to have as many
> unused release tags (e.g. 2.4_alpha1) because something got fixed after
> tagging but before release.
>
> --
> Samuli Seppänen
> Community Manager
> OpenVPN Technologies, Inc
>
> irc freenode net: mattock
>
>
> [1] Essentially "apt-get/yum/dnf for Windows":
>
>     <https://chocolatey.org/>
>
>
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Reply via email to