Re: [cdt-dev] Migration of CDT Jenkins

[William Riley <william.riley@xxxxxxxxxxx>]

Thanks Jonah for the extra info & reminding me I forgot to include the password!

 

Once the images are in their final locations I’ll update the GitHub repo to include instructions for running locally. One change already, I’ve pushed an additional label “stable-ubuntu-16.04” which will (hopefully) not get broken by changes made prior to testing in Jenkins. I had hoped to set up automated builds for the docker files in Travis CI but they generate too much log data (they have a 4MB limit).

 

I’ve now got the Gerrit builds mostly working, though there is a problem with the permissions on “cdt Bot” so the review scores aren’t posted to Gerrit, already mentioned on the migration Bugzilla. If you want to check the triggers just push with a topic of “CDT_JIRO_MIGRATION”, this topic will trigger the new Jenkins but not the old one.

 

I’ve raised https://bugs.eclipse.org/bugs/show_bug.cgi?id=545624 to track issues CDT side.

 

Currently still to do:

• Tools.templates builds (planned to complete tomorrow)
• Launchbar builds (planned to complete tomorrow)
• Upload to nightly area (planned to complete tomorrow)
• Releng build jobs (will look at once other jobs done)

 

At the moment I’m simply setting up the pipeline scripts in the Jenkins UI. Once they are working I will look at moving them into Git, either under cdt-infra or the main cdt repo, that way we can share the pod templates between pipelines much more easily.

 

Regards

William

 

From: cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx> On Behalf Of Jonah Graham
Sent: 21 March 2019 01:01
To: CDT General developers list. <cdt-dev@xxxxxxxxxxx>
Subject: Re: [cdt-dev] Migration of CDT Jenkins

 

Hi William,

 

This is great. I have run the build on my machine. I have not had exactly the same sets of failures, but certainly close enough to progress on resolving test failures. I will look at DSF ones first.

 

For all:

 

A couple of pieces of useful information:

 

1- If you want to build on your machine but share the maven cache and use the checkout of CDT on your machine you can do this:

 

docker run --rm -it -p 5900:5900 -v $PWD/org.eclipse.cdt:/home/cdt/work -v ~/.m2:/home/cdt/.m2 -u $(id -u)  quay.io/kummallinen/cdt-infra-eclipse-full:ubuntu-16.04 bash

 

The first -v mounts my host clone / checkout of CDT into the container. The second -v mounts my host .m2 directory so I don't have to redownload everything on each run. 

 

2- The VNC password is 123456 

 

Thanks,

Jonah

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

 

 

On Wed, 20 Mar 2019 at 15:57, William Riley <william.riley@xxxxxxxxxxx> wrote:

Hi all

 

CDT is scheduled to move to the new Jenkins system (JIRO) on Friday.

 

I’ve managed get the main CDT build working in under the new system now, however there are around 26 tests that are failing consistently when run inside the new container environment that will need to be addressed. Most of these failures are in the GDB tests but also a number of Meson UI tests are failing. See https://ci-staging.eclipse.org/cdt/job/cdt-master-pipelinetest/64/testReport/ for the full list.

 

Unless anyone has any objections I will go though tomorrow and disable these tests until they can be fixed. I’ll be create new pipelines for the Gerrit verification builds tomorrow ready for the final switch over.

 

If you want to try to run the tests under the same environment as the build system the Docker images are available and can be used to help debug the tests. For they are temporarily hosted on quay.io under my own account, unfortunately there isn’t yet any official place to host these. We should at least try to move them under an “eclipse-cdt” org on either quay.io or Docker Hub. (@Doug Schaefer any comments how to do this?)

 

The actual docker files will be on GitHub: https://github.com/eclipse-cdt/cdt-infra and until the pull request is merged you can see them @ https://github.com/eclipse-cdt/cdt-infra/pull/1

 

You can run a build inside the container locally and connect a VNC client to monitor SWTBot tests. E.g.

 

Run the container in interactive mode:

> docker run --rm -it -p 5900:5900 quay.io/kummallinen/cdt-infra-eclipse-full:ubuntu-16.04 bash

 

Then inside the container run:

> ~/.vnc/xstartup.sh

> mkdir work && cd work && git clone https://git.eclipse.org/r/cdt/org.eclipse.cdt.git .

> /usr/share/maven/bin/mvn clean verify -Pbuild-standalone-debugger-rcp -Ddsf.gdb.tests.timeout.multiplier=10 -Dindexer.timeout=300

 

 

Regards

William

 

Renesas Electronics Europe GmbH,Geschaeftsfuehrer/President : Michael Hannawald, Sitz der Gesellschaft/Registered office: Duesseldorf, Arcadiastrasse 10, 40472 Duesseldorf, Germany,Handelsregister/Commercial Register: Duesseldorf, HRB 3708 USt-IDNr./Tax identification no.: DE 119353406 WEEE-Reg.-Nr./WEEE reg. no.: DE 14978647

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

Renesas Electronics Europe GmbH,Geschaeftsfuehrer/President : Michael Hannawald, Sitz der Gesellschaft/Registered office: Duesseldorf, Arcadiastrasse 10, 40472 Duesseldorf, Germany,Handelsregister/Commercial Register: Duesseldorf, HRB 3708 USt-IDNr./Tax identification no.: DE 119353406 WEEE-Reg.-Nr./WEEE reg. no.: DE 14978647