Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tracecompass-dev] [OI2JIRO] Migration of TraceCompass JIPP to new CI infrastructure

Hi Jonah

 

Thanks for the information. I’m still learning how to use the new setup. I recently realized that we can ask to assign our allocation that comes with the foundation membership and I’ve opened a bug to request this.

 

BTW, your and CDT’s work to setup JIRO has been already a great help for me because I was able to check how you did certain things. Thanks a lot for the lead way on that :-)

 

BR

Bernd

 

From: tracecompass-dev-bounces@xxxxxxxxxxx <tracecompass-dev-bounces@xxxxxxxxxxx> On Behalf Of tracecompass developer discussions
Sent: Thursday, December 19, 2019 3:37 PM
To: tracecompass developer discussions <tracecompass-dev@xxxxxxxxxxx>
Subject: Re: [tracecompass-dev] [OI2JIRO] Migration of TraceCompass JIPP to new CI infrastructure

 

Hi Bernd,

 

If it is helpful.... When CDT was first moving to JIRO, William Riley spent some time on tuning vCPU and RAM to get the best result. In the end for the bigger jobs we settled on 1.3 vCPUs and 2.6G ram, and for the rest, 1 vCPU and 1G or 1.75G (Depending on whether maven is running). Also, if Ericsson is still a member of the foundation, it can "donate" its allocation to tracecompass so you can have more resources.

 

HTH,

Jonah

~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com

 

 

On Thu, 19 Dec 2019 at 13:16, tracecompass developer discussions <tracecompass-dev@xxxxxxxxxxx> wrote:

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
Sent: Tuesday, July 30, 2019 10:45 AM
To: tracecompass developer discussions <tracecompass-dev@xxxxxxxxxxx>
Subject: Re: [tracecompass-dev] [OI2JIRO] Migration of TraceCompass JIPP to new CI infrastructure

 

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
Sent: Monday, April 8, 2019 11:22 AM
To: tracecompass developer discussions <tracecompass-dev@xxxxxxxxxxx>
Subject: Non-compliant mail – action required, contact dmarc@xxxxxxxxxxx : [tracecompass-dev] [OI2JIRO] Migration of TraceCompass JIPP to new CI infrastructure

 

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

 

_______________________________________________
tracecompass-dev mailing list
tracecompass-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/tracecompass-dev

Back to the top