| Re: [tracecompass-dev] [OI2JIRO] Migration of TraceCompass JIPP to new CI infrastructure |
|
Hi, Some updates on the migration. Most of the jobs have been migrated and are currently running on the staging ci server [1]. We are supposed to switch the new environment by the end of the year. After migration we will be only able to run
1 build at a time which will cause some bottleneck for Gerrit patches. This is due the assigned number of vCPUs (2) and RAM (8GB) available by default for each project.
After the migration we will have investigate how to improve the situation. One idea would be to run Trace Compass incubator Gerrit job on the external slave that we have. Another idea is to limit each build to 1 vCPU at a time but this
is not preferable. Other options will be looked at as well. Thanks Bernd [1] https://ci-staging.eclipse.org/tracecompass From: tracecompass-dev-bounces@xxxxxxxxxxx <tracecompass-dev-bounces@xxxxxxxxxxx>
On Behalf Of Bernd Hufmann Hi Just an update on this one. The migration is still ongoing. It seems to be more involving than expected. Simon Delisle is working hard on the migration. Currently, you might see some extra Gerrit verification job entries in Gerrit patches with the name “Trace Compass Bot”. Please ignore it and remove it from the review (especially if it put -1). BR Bernd From:
tracecompass-dev-bounces@xxxxxxxxxxx <tracecompass-dev-bounces@xxxxxxxxxxx>
On Behalf Of Bernd Hufmann Hi, Just to let you know, that the Trace Compass JIPP is going to be migrated to the new CI infrastructure soon. This will have some impact on the Trace Compass Jenkins jobs (also incubator) during the migration, but the migrated jobs should
be up and running soon after. See wiki [1] about the background of the migration, and you can follow the migration on bug [2]. BR, Bernd [1] https://wiki.eclipse.org/CBI/Jenkins_Migration_FAQ [2]
https://bugs.eclipse.org/bugs/show_bug.cgi?id=546149 |