Windows runner for CI now generally available!
Hi everyone, Good news! Thanks to OpenAtMicrosoft and our staff we have set up a Windows runner for the GNOME/ group. Right now it's a single runner with the "windows" tag attached, feel free to use it as you see fit. *How to use it* Here's is an example on how to use a specific runner with a tag: https://gitlab.gnome.org/GNOME/gtk/blob/master/.gitlab-ci.yml#L43 For the new Windows runner, the CI configuration would be something like: windows job: stage: - build tags: - windows More documentation about tags: https://docs.gitlab.com/ee/ci/yaml/README.html#tags *A report to Microsoft* Part of the the deal for getting the keys is that we will write a report to Microsoft. If you start using the runner regularly, could you write to me in an email a short summary about how are you using the Windows runner and how that benefits us and our users using Windows or Microsoft platforms? *+ other Microsoft product keys* Additional good news is that we also got some Microsoft product keys such as Visual Studio Ultimate, Office 365, Office Professional, Outlook, .Net, Windows 10, Visio Professional, Visual Basic, Exchange, etc. If you have a strong use case that would be of benefit for the GNOME project and community please reach out to me so we can discuss it. Lastly, let Bartłomiej, Andrea or me know if the runner is working well for you. Cheers, Carlos ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Windows runner for CI now generally available!
On Tue, 19 Nov 2019 at 10:48, Carlos Soriano wrote: > Hi everyone, > > Good news! Thanks to OpenAtMicrosoft and our staff we have set up a > Windows runner for the GNOME/ group. Right now it's a single runner with > the "windows" tag attached, feel free to use it as you see fit. > > *How to use it* > Here's is an example on how to use a specific runner with a tag: > https://gitlab.gnome.org/GNOME/gtk/blob/master/.gitlab-ci.yml#L43 > > For the new Windows runner, the CI configuration would be something like: > windows job: > stage: > - build > tags: > - windows > > More documentation about tags: > https://docs.gitlab.com/ee/ci/yaml/README.html#tags > > *A report to Microsoft* > Part of the the deal for getting the keys is that we will write a report > to Microsoft. If you start using the runner regularly, could you write to > me in an email a short summary about how are you using the Windows runner > and how that benefits us and our users using Windows or Microsoft platforms? > > *+ other Microsoft product keys* > Additional good news is that we also got some Microsoft product keys such > as Visual Studio Ultimate, Office 365, Office Professional, Outlook, .Net, > Windows 10, Visio Professional, Visual Basic, Exchange, etc. If you have a > strong use case that would be of benefit for the GNOME project and > community please reach out to me so we can discuss it. > FYI I didn't receive many requests about these, maybe we can lower the bar and remove the "strong" from "strong use case" here :) Seriously, don't hesitate to let me know if any of these would be of interest for you, we can discuss whether that usage is appropriate or not. > > Lastly, let Bartłomiej, Andrea or me know if the runner is working well > for you. > > Cheers, > Carlos > ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Windows runner for CI now generally available!
On Tue, Nov 19, 2019 at 10:49 AM Carlos Soriano via desktop-devel-list wrote: > > Hi everyone, > > Good news! Thanks to OpenAtMicrosoft and our staff we have set up a Windows > runner for the GNOME/ group. Right now it's a single runner with the > "windows" tag attached, feel free to use it as you see fit. Is there any documentation for the runner? Like which executor is used, what is installed on it and where, can it handle parallel builds etc. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
