These instructions explain how to recreate the windows-10 template with OpenSSH server and Chocolatey. Create a Windows 10 slave This page supposes that a slave has been created in a project in https://qlf-ci.inria.fr from one of the two templates Win10-CI-2-GTE or windows-10 (Community tab). windows-10 template is derived from Win10-CI-2-GTE with an Open SSH server and Chocolatey installed: these steps are documented below. Choose Medium instance-W10: 2x2 GHz + 4 GB RAM for “Computer offering”.

Introduction The windows10-choco-java-virtio template (in the Featured tab) provides a Windows 10 installation with a native OpenSSH server and Chocolatey. You may connect a fresh instance of this template via SSH or rdesktop. SSH connections use the cmd.exe as default shell. You may change the default shell for Powershell, or the Cygwin bash, or the bash provided by the Windows subsystem for Linux. Chocolatey is a package manager for Windows. You may use it to install the development tools that you need.

REDIRECT ../main_page

CloudStack is the cloud middleware used by the Inria Continuous Integration service. It permits to create and administrate virtual machines used as Jenkins/Gitlab runners (i.e., virtual machines for automated builds). This page describes different ways of virtual machines creation with CloudStack from a template or an ISO. This is an alternative much more complicated compared to Virtual Machine creation from the web portal and you may have to deal with a fine tuning of your virtual machine administration.

This page explains how to add password reset feature to virtual machines (useful for template creation). The password reset feature, if enabled in Template, will reset the password at instance generation. Note: This is taken directly from the CloudStack manual. It has not been tested To activate this in a template, you need to install extra script in your VM: For windows, download the installer CloudInstanceManager.msi and run it in the Windows VM.

Users are welcomed to share their knowledge related to: general concepts and good practices about continuous integration advanced usage of Jenkins creation of slave template with non-featured operating systems, see this page for more information. etc A good idea is to: subscribe to the dedicated mailing-list: ci-community send a message to ci-community@inria.fr when you want to share a useful experience If you want to write a specific documentation or modify the existing one, documentation can be found in the following public gitlab repository.

TODO Providing custom build slaves using the CloudStack portal Slaves instances are obtained through CloudStack; refer to the CloudStack documentation and to the CloudStack tutorial. In the following sections, we assume that you have created a build slave, know its IP address and can SSH into it (using a newly-created ci account, for instance). Note (2012-08-03): new instances come by default with a root account (password: password). Note (2012-11-06): new windows instances come by default with an administrator account named ci (password: ci).

Prerequisites To use SSH to communicate with the SSH gateway ci-ssh.inria.fr, you need an OpenSSH client (which comes pre-installed on GNU/Linux, macOS, and Windows 10), with an SSH version 6.5 or later (earlier versions used an MD5 signature, which is not secure). To view the version of SSH installed on your system, run ssh -V. Recommended SSH key types ED25519 SSH keys: more secure and performant than RSA keys. OpenSSH 6.

The purpose of this page is to provide advices to create CloudStack linux templates ready to use for others as Community Templates. The page is divided in 3 parts, what seems to be common to all linux Systems what is specific to Debian Systems what is specific to RedHat Systems Community templates Caution When creating a qcow2 template, ensure that it follows the qcow2 v2 format, otherwise it won’t work on CI.

General How can I get help? You can contact the support through the ci-support@inria.fr mail address. I have multiple projects to set up. Should I create multiple Jenkins projects in the portal or should I create a single Jenkins project with multiple jobs ? Short answer: if these projects concern the same group of developers and/or if they have dependencies with each other, then you may prefer to create a single Jenkins project.