Besides using Jenkins, you can use gitlab’s integrated CI pipelines. You can either use one of the shared runners (Linux only) or set up a CI runner on a machine (it can be any machine, for instance one of your own machines, or a VM hosted in the CI cloudstack). Enabling CI on a gitlab project In your project’s General settings, in the section Visibility, project features, permissions, search for CI/CD, and check the feature is enabled.

This document describes the process of configuring Jenkins and setting up build slaves on INRIA’s continuous integration platform. It is not meant to be a comprehensive docementation for Jenkins. If you need further details about Jenkins, then you should consult the official documentation. Prerequisites This tutorial assumes that: Step 1: you have a user account on https://ci.inria.fr/ and that you created a project (or been invited to an existing project) Step 2: you can open remote sessions (ssh/rdesktop) to your slave virtual machines Connecting to your Jenkins instance Each project registered on https://ci.

Maintenance on the CI web portal on tuesday, september 22th 2020 A maintenance on the CI web portal is scheduled for next Tuesday (september 22th) The web portal (https://ci.inria.fr/) will be unavailable during this maintenance. User operations done by the portal will be affected: projects creation / deletion users lists modification slaves creation (using the portal) So please don’t plan to perform this kind of operations during this day. You can do them earlier, or postpone them to wednesday.

Use case This procedure applies to Windows VMs crashing because of an invalid Virtio Storage driver. The boot triggers a BSOD related to viostor.sys. Solution Remove the viostor.sys driver manually. Procedure 1. boot windows in the Startup Repair mode 2. cancel the automatic repair (it will fail anyway) 3. in the final screen, select View advanced options for system recovery and support 4. log in as user ‘ci’ 5. select command prompt

Any ‘slave’ virtual machine created on https://ci.inria.fr/ (or https://ci-cloud.inria.fr) is accessible by ssh bouncing through the SSH gateway ci-ssh.inria.fr. This page explains how to connect through SSH to a virtual machine. Once connected, you will be able to perform any administration task (like installing the packages you need to build your software). Note: some packages (JDK, Ant and Maven especially) can be automatically installed by Jenkins. You may prefer not to install them manually.

Mac Mac OSX 10.9 Screen saver The screen saver is activated and is taking CPU and memory : $ ps ax | grep -i screensaver | grep -v grep 612 ?? Us 11479:59.42 /System/Library/Frameworks/ScreenSaver.framework/Versions/A/Resources/ScreenSaverEngine.app/Contents/MacOS/ScreenSaverEngine -loginWindow You can desctivate it this way in command line : $ sudo su -l "ci" -c "defaults -currentHost write com.apple.screensaver idleTime 0" You can check it this way : $ defaults -currentHost read com.apple.screensaver idleTime

Jenkins Pipeline Since the version 2.x of Jenkins, the user which creates jobs or “items” could use pipelines to organize the continuous integration (CI) process. This way enables the user to store the quasi-entire configuration of CI in a JenkinsFile who can be store on the SCM repository. Thus, there is anymore need to make tedious configuration by clicking. In this tutorial we will present a basic usage of Jenkins pipelines

The objectives of this charter are: to recall the legislative framework and the general deontology that applies to information made available on the Internet; to define the conditions for hosting projects on the Inria Continuous Integration server; to define the responsibilities accepted when using the Inria Continuous Integration service, which is available on the server ci.inria.fr, and the associated Cloud platform, available on ci-cloud.inria.fr. The general legislative framework The opening of a project and its activity are regulated by the laws relative to the dissemination and diffusion of intellectual works.

Using Jenkins CI with a Gitlab Repository Introduction In this tutorial, we want to help the user to run the Jenkins Continuous Integration Service along the Gitlab platform. At the end of the configuration, your project will behave typically like : runs automatically jobs on CI/Jenkins when a commit is pushed on the master branch in Gitlab checkouts the changes in the sources of your Gitlab project perform the build of the project (code generation, compilations, tests, code inspection, etc.

Introduction This tutorial explains how to create a project on the Inria Continuous Integration Web portal, and its relation with Jenkins and CloudStack. Jenkins and CloudStack Firstly, Continuous integration require to manage all the testing process. For example, one could want the testing process to be triggered by every commit on a SVN server, and consist in updating the sources, recompiling what has changed, running a test suite, generating and serving HTML report, and sending email if some tests failed.