Bonjour aux utilisateurs de Jenkins,

Le comité de pilotage de l’Atelier de Production Logicielle Inria a décidé que l’infrastructure mutualisée hébergeant les projets Jenkins sera arrêtée au 30 septembre 2026, notamment pour des raisons de sécurité et de ressources humaines.

Par conséquent, vous êtes d’ici là vivement encouragé à migrer vers une autre technologie, telle que gitlab-ci ou github action.

Toutefois, si votre projet ne peut pas se passer de Jenkins, vous pouvez bénéficier d’une VM dédiée hébergeant une instance préinstallée de Jenkins selon l’offre de service suivante, résultat d’un travail de longue haleine avec les collègues de l’Intégration Continue et qui a été validée sur un projet phare :

https://doc-si.inria.fr/spaces/SU/pages/306348342/Jenkins

Les demandes de migration sont à faire avant le 21 août 2026 via un ticket sur https://helpdesk.inria.fr/categories/424/submit.

Une journée d’interruption de service étant à prévoir, l’été pourrait être propice à la migration.

Respectueusement,

L’équipe Atelier de Production Logicielle

Hello Jenkins users,

The steering committee of the Inria Software Production Workshop has decided that the shared infrastructure hosting Jenkins projects will be shut down on September 30, 2026, primarily for security and human resources reasons.

Therefore, you are strongly encouraged to migrate to another technology, such as GitLab CI or github action, by that date.

However, if your project cannot do without Jenkins, you can take advantage of a dedicated VM hosting a pre-installed instance of Jenkins under the following service offering, which is the result of a long-term collaboration with our Continuous Integration colleagues and has been validated on a flagship project:

https://doc-si.inria.fr/spaces/SU/pages/306348342/Jenkins

Migration requests must be submitted by August 21, 2026, via a support ticket at https://helpdesk.inria.fr/categories/424/submit.

Since a one-day service interruption is expected, summer might be a good time to carry out the migration.

Sincerely, The Software Production Workshop Team

Bonjour,

Le template “MacOS Tahoe” a été mis à jour.

Voici les corrections apportées:

• Passage de la version 26.2 vers la version 26.5.1.
• Accès à l’interface graphique via SSH+VNC
• Version java: openjdk 21.0.11

La nouveau template se nomme: CI-MacOS-Tahoe-26.5.1_xcode_gitlab-runner.

Pour rappel, le lien vers la documentation pour les templates MacOS.

Cordialement, L’équipe PFO

Hi,

The “MacOS Tahoe” template has been updated.

Here are the changes made:

• Upgrade from version 26.2 to version 26.5.1
• Access to the graphical interface wit SSH+VNC
• Java version: openjdk 21.0.11

The new template is named: CI-MacOS-Tahoe-26.5.1_xcode_gitlab-runner.

As reminder, here is the link to the documentation for MacOS templates.

Best regards, The PFO team

Bonjour,

Un nouveau template est disponible pour vos VMs sur CloudStack :

CI-MacOS-Tahoe-26.2_xcode_gitlab-runner

Profitez-en !

L’équipe CI

Hello,

A new template is available for your VMs on CloudStack:

CI-MacOS-Tahoe-26.2_xcode_gitlab-runner

Enjoy! The PFO team

Cordialement, L’équipe PFO.

Un nouveau runner d’instance gitlab est disponible avec plus d’espace disque (40 Go). Vous pouvez l’utiliser avec les tags suivants: ci.inria.fr, linux, large_more_disk.

Pour plus de détails sur les runners d’instance partagés, cf. doc

Cordialement, L’équipe PFO.

A new gitlab instance runner is available with more disk space (40GB). You can use it with the following tags: ci.inria.fr, linux, large_more_disk.

For more details about shared instance runners, cf.doc

Yours sincerely, The PFO team.

Le 10 juin 2025 les anciens runners gitlab partagés identifiés avec les tags ci.inria.fr et v2018 seront définitivement arrêtés, laissant place aux nouveaux runners v2025 en service depuis mars.

Les jobs marqués avec les tags ci.inria.fr et v2018 ne seront plus exécutés. Nous vous invitons dès maintenant à retirer le tag v2018 (ou à le remplacer par v2025) pour utiliser les nouveaux runners.

Les jobs marqués avec le tag ci.inria.fr mais sans le tag v2018 ne sont pas affectés : ils utilisent déjà les nouveaux runners.

détails

Cordialement, l’équipe CI.

On June 10, 2025 the old gitlab shared runners identified with tags ci.inria.fr and v2018 will be definitely shut down, succeeded by the new runners v2025 active since March.

Jobs tagged with ci.inria.fr and v2018 will no longer be executed. We invite you to remove the v2018 tag (or to replace it with v2025) so as to use the new runners.

Jobs tagged with ci.inria.fr but without v2018 are not affected: they are already using the new runners.

details

Yours sincerely, the CI team.

Bonjour aux utilisateurs de la CI,

Nous sommes fiers de vous annoncer que l’opération de mise à jour sur la CI est terminée : tout est rentré dans l’ordre.

Cette opération a été préparée depuis plusieurs mois par nos équipes. Leur coordination ces 3 derniers jours a permis de résoudre rapidement tous les imprévus liés à ce grand saut dans le temps : passage à java 17, Python 2 -> Python 3, Ubuntu 16 à 24 !

Je tiens à remercier tous ceux qui se sont mobilisés et synchronisés pour que cette opération soit un succès avec une durée d’indisponibilité la plus courte possible. Bravo à vous !

Avec nos excuses pour la gêne occasionnée, nous vous souhaitons désormais une joyeuse utilisation de la CI.

L’équipe CI

Hello CI users,

We are proud to announce that the IC update operation is now complete: everything is back to normal.

This operation has been prepared for several months by our teams. Their coordination over the last 3 days has enabled us to quickly resolve all the unforeseen events associated with this great leap forward in time: switch to java 17, Python 2 -> Python 3, Ubuntu 16 to 24!

I’d like to thank everyone who rallied round and synchronised their efforts to make this operation a success, with the shortest possible downtime. Well done to you all!

With apologies for any inconvenience caused, we hope you enjoy using the CI from now on.

The CI team

Le 14 avril 2025 entre 8H00 et 12H00, le portail ci.inria.fr sera arrêté pour mettre à jour les serveurs. Tous les serveurs Jenkins seront également impactés. L’OS des machines support va être mis à jour afin de permettre entre autres le passage à java 17.

Nous nous excusons par avances de la gène accasionnée.

Cordialement, l’équipe CI.

On April 14, 2025 between 8:00 AM and 12:00 AM, the ci.inria.fr portal will be shut down to update the servers. All Jenkins servers will also be impacted. The OS of the support machines will be updated to enable java 17.

We apologize in advance for any inconvenience.

Yours sincerely, the CI team.

Chers utilisateurs CI,

Depuis quelques temps nous constatons des difficultés pour démarer des VMs Cloudstack utilisant un grand nombre de coeurs CPU. Le démarage est en erreur avec un message “Unable to start a VM due to insufficient capacity”. Nous cherchons un moyen d’accroitre les capacités CPU du service mais celà va prendre du temps.

En attendant, pour que chacun puisse profiter pleinement de Cloudstack nous vous enjoignons fortement à éteindre toutes les VMs qui ne servent pas. Vous pouvez égelement utiliser un quadriciel comme opentofu pour créer et supprimer des VMs à la demande. Vous trouverez un exemple d’utilisation d’opentofu dans la gallery d’exemples CI ici.

Cordialement,

L’équipe CI

Dear CI users,

For some time now we’ve been experiencing difficulties starting Cloudstack VMs using a large number of CPU cores. The startup error is “Unable to start a VM due to insufficient capacity”. We’re looking for a way to increase the service’s CPU capacity, but it’s going to take some time.

In the meantime, so that everyone can take full advantage of Cloudstack we strongly urge you to turn off all VMs that are not in use. You can also use a framework like opentofu to create and delete VMs on demand. You’ll find an example of how to use opentofu in the CI example gallery here.

Best,

The CI Team

Chers utilisateurs CI,

Suite aux rappels envoyés par e-mail début mai et début juin, nous vous informons que les serveurs Jenkins dont la version est antérieure à la version 2.440.3 LTS au 9 juillet 2024 seront supprimés des serveurs.

Cordialement,

L’équipe CI

PS: si vous avez explicitement demandé un délai pour la montée en version, ne tenez pas compte de ce message.

Dear CI users,

Further to reminders sent by e-mail at the beginning of May and June, we would like to inform you that Jenkins servers with versions prior to version 2.440.3 LTS on July 9, 2024 will be removed from the servers.

Best,

The CI Team

PS: if you have explicitly requested an upgrade deadline, please disregard this message.

Chers utilisateurs CI,

Rencontrant pas mal de problèmes de maintenance sur les serveurs Jenkins, nous avons décidé d’enlever de l’interface utilisateur la possibilité d’activer Jenkins à la création d’un projet CI. Cependant, vous pourrez toujours créer un ticket helpdesk (https://helpdesk.inria.fr/categories/320/submit) si vous souhaitez avoir Jenkins.

Cordialement,

L’équipe CI

Dear CI users,

As we are regularly facing maintenance issues with Jenkins servers, we have decided to remove from the user interface the option to activate Jenkins when creating a CI project. However, you will still be able to create a helpdesk ticket (https://helpdesk.inria.fr/categories/320/submit) if you wish to use Jenkins.

Best regards,

The CI Team

A maintenance operation requires us to stop all CI jenkins servers. This operation will take place tomorrow, Thursday December 14 at 1:30 pm. It should last half an hour.

Once the servers have been restarted, your jenkins projects may remain switched off. You may have to restart them manually on ci.inria.fr.

We apologize for the inconvenience.

We will be updating and restarting some machines in charge of our infrastructure tomorrow, Tuesday, November 21, between 1:30 pm and 2:00 pm. This update is expected to be brief. While the virtual machines should not be impacted, all services related to user accounts, including login, will be temporarily unavailable.

We apologize for any inconvenience and will endeavor to minimize the downtime. Thank you for your understanding.

Apple hypervisors will be shutdown from Monday 26 June 6pm till Tuesday 27 June 9pm for maintainance.

Sorry for the inconvenience.

Dear CI users,

The LDAP certificate for ci.inria.fr has been renewed: the certificate was expired on 2023/04/05 and login was impossible on that day on CI portal (ci.inria.fr) and CloudStack (login on virtual machines still worked). You should no longer have difficulties to login on CI anymore.

Sorry for the inconvenience.

There is a new featured template for Ubuntu 20.04 LTS amd64 (ubuntu-20.04-lts). This template subsumes the former template Ubuntu 20.04 amd64, which is no longer featured.

Changes with respect to the former template:

• the initialization service for ‘~ci/.ssh/authorized_keys` is fixed, and the contents of this file will no longer be reset on each boot;
• cloud-init is now configured to consider CloudStack provided user-data by default;
• packages are upgraded to their last available version.

Thank you very much for using CI.

CloudStack is now updated to 4.16. You should now be able to start your virtual machines again via the portal ci.inria.fr or via CloudStack API or web interface.

You may refer to the portal documentation: https://inria-ci.gitlabpages.inria.fr/doc/page/web_portal_tutorial/#slaves

Thanks to this update, Mac OS Catalina and Mojave are supported, and nested KVM is enabled.

Thank you very much for using CI.

CloudStack is now updated to 4.16. You should now be able to start your virtual machines again via the portal ci.inria.fr.

You may refer to the portal documentation: https://inria-ci.gitlabpages.inria.fr/doc/page/web_portal_tutorial/#slaves

We still have a problem that prevents users to log in to CloudStack by the web interface. Only the CloudStack web interface seems to be affected: you are still able to manage your virtual machines via the portal or the CloudStack API. We will fix the connection to the web interface as soon as possible.

Thank you and sorry for the inconvenience.

All VMs hosted on ci.inria.fr will be interrupted on Tuesday afternoon 2023-02-07, 2pm-6pm, for CloudStack maintenance. CloudStack will be upgraded to 4.16, and nested KVM will be enabled. The actual interruption may be shorter, we will publish an announce when the platform will be back. You will have to restart the VMs manually via ci.inria.fr or CloudStack. Thank you!

The option --ajpPort13=-1 has been removed for launching Jenkins. This option was necessary for very old version of Jenkins, but was ignored by all currently deployed Jenkins instance, and is no longer supported since Jenkins 2.375 (released on 2022-10-25). If you experienced failure while updating Jenkins recently, you should have a try now. Thank you!

Happy new year!

The shared storage for Jenkins instance is back to normal since last Thursday. If your Jenkins instance is down due to disk space outage, restarting the instance should now work again. Sorry for the inconvenience, we will try in the next few days to take counter-measures to prevent these kinds of problems in the future.

The shared storage for Jenkins instance is full: this probably prevents all Jenkins instances to work properly. We are currently investigating why we have difficulties to free space and I hope we will be able to restore the service very soon!

The certificate of the LDAP server was expired this morning and has been renewed. You may have had some difficulties to connect to ci.inria.fr, CloudStack and Jenkins instances this morning but everything should work again now! Sorry for the inconvenience.

You may have received this morning some emails inviting you to extend the expiration date of your CI virtual machines. As you may have noticed, the URLs were wrong: /prolongation was missing at the end. You may either use the fixed URL, or the “Extends” button in the slave table in the web interface of your CI project.

Sorry for this inconvenience, and thank you for extending your VMs!

We are pleased to announce that shared docker runners are now available for gitlab.inria.fr!

Thanks to everyone who helped testing the service during the (very long!) beta period. You can right now enable the shared runners in the CI/CD settings of your Gitlab projects.

See the shared runners documentation for more details. The three following docker runners are available:

• small (1 CPU, 2048 MB RAM), tags: ci.inria.fr, linux, small
• medium (2 CPUs, 4096 MB RAM), tags: ci.inria.fr, linux, medium
• large (4 CPUs, 8096 MB RAM), tags: ci.inria.fr, linux, large

The runners will handle jobs declared in the .gitlab-ci.yml file of the project repository, at the condition that the jobs have at least one tag among ci.inria.fr, linux and either small, medium or large (these three last tags are exclusive: they cannot be used together for the same job since no runner will match more than one of them).

We would like to send a big thank you to Anthony Baire for all his efforts in developping this service, and we would like to thank also the CI infrastructure team of the Inria DSI who helped in deploying the platform.

Thank you very much for using ci.inria.fr, and happy hacking!

For a few days and for an unknown reason, Mac OS X VMs are continuously rebooting when they are newly created or when their offer is changed. We are aware of the problem and are trying to fix it as soon as possible.

Thank you for your understanding!

Each VM hosted by ci.inria.fr has now an expiration date, fixed in one year from now for current VMs, and one year after the creation date for future VMs. This rule will make us able to clean unused VMs and save ressources for new projects.

These expiration dates are freely renewable, using the dedicated button “Extend” in the VM list associated to a project in the portal ci.inria.fr.

When VMs are about to expire, project admins will be reminded three times by email (with a link to extend the expiration date) starting three weeks before the expiration. Expired VMs will be deleted and project admins will be notified (there will be a 24h delay before expunging, during which the VM can be recovered).

Thank you for your understanding!