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.

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.

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.

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.

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.