Inria Continuous Integration service will be down Tuesday, July 18th, 2017 to allow maintenance of the service.
Jenkins servers operating systems will be upgraded and some security improvements will be applied.
The service should be back at the end of the day.
Inria continuous integration service is being modernized. Machines part of the infrastructure are being updated by DSI-SESI. CI teams work on providing up-to-date featured templates for the service (Fedora, Cent Os, Ubuntu, Debian, Windows). They also work on supporting latest Jenkins versions (Jenkins 2.x) offering new possibilities to users (ease pipeline management and continuous deployment) but needing a review of projects creation process on the Inria service. Migration from Jenkins 1.x to Jenkins 2.x is also problematic in some cases. A migration guide will be provided.
The precedent incident about partition saturation is closed.
The partition size of CI has been increased from 3.3 to 4.0 Tb.
To prevent partition from becoming bloated, do not forget discarding old build records after a specific time period has passed and/or after a specific number of builds have been run. This policy can be set on your job’s configuration page.
The partition hosting all the projects on continuous integration service is full.
The incident has appeared at 6:00 pm today, Wednesday July 13th, just at the beginning of a long week-end.
It is certainly not possible to fix the problem before Monday July 18th.
Sorry for the trouble.
After a great work performed by the IT operational team team, CloudStack (the software used to manage CI slaves) has been upgraded to the 4.4.2 version. Since we do not have any idea about the slaves that are really used in the projects, automatic restart cannot be performed, and* you have to restart slaves manually*. The maintenance is not fully finished as it is not yet possible to create new slaves. We will keep you informed on this problem.
As well as the CloudStack upgrade, a new version of the portal has been deployed. It includes libraries update, some bug fixes and minor changes visible on the portal (better display of news, logs).
The CI team.
After a great work performed by the IT operational team and the development team, it's our pleasure to announce that the continuous integration service is available. Since we do not have any idea about the slaves that are really used in the projects, automatic restart cannot be performed, and you have to restart them manually.
Please accept our apologies for this unexpected downtime.
The CI team.
There is currently an issue with the CloudStack platform leading to unreachable slaves and some errors when trying to manage your project.
The IT operational team is working on this problem and they do their best to have the CloudStack up soon.
Sorry for the inconvenience,
The CI team.
We are happy to declare the Inria Continuous Integration service open today January 29, 2013. Starting from this web portal, you can create a project and then :
Take a look at the on-line documentation (https://wiki.inria.fr/ciportal) for more information about this service.
If you want to know more on the continuous integration methodology, here is a very good post by Martin Fowler. Note that in the Inria research centers the local SED is also available to talk with you about continuous integration. Note that more than twenty selected projects beta-tested this service with various programming languages, build tools, test libraries, etc. Those experiments allowed us to populate the FAQ. Take time to read it, to contribute your experiments, and to discuss and share knowledge via the mailing list ci-community at inria dot fr or by contacting the support team.
Today (October, the 31st), the Inria continuous integration platform is open to beta-testers selected in all Inria research centers. Enjoy!