Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cbi-dev] Interrogations on the new Jenkins/Kubernetes instances

Hi Quentin,

See my answers inline

Le 6 juin 2019 à 17:58, LE MENEZ Quentin <Quentin.LEMENEZ@xxxxxx> a écrit :

Hi Everyone,
I might be asking something that is already documented, and if so please direct me to the relevant documentation, but if not here are my questions:
For context I was configuring the XWT jobs on and I am not admin of this instance.
1-      The xwt-master workspace just vanished without any actions from me (so I gather the message The agent this project has run on for the last time was removed indicates me that the pod/node was used by another job hence the workspace was deleted ?). How so ?

Agents on the new infra are spawn on-demand, a new workspace is created at the same time and everything is teared down once the build is done. If you want some files to outlive the duration of the jobs, you should either use the archiveArtifacts Jenkins feature and/or cp the files to the download area ( Note that if you push files that are not releases, you should put them in a folder strcuture that will not be mirrored (see for the list of file patterns that are not send to mirrors).

2-      I cannot seem to be able to run the zip command from a shell script build step. Should I use something else ?

"zip" command is not available in the default agent image, "unzip" is though. Advanced images are available in "migration" and "ui-test" agents. See for how to use them.

3-      The gerrit Job can’t seem to add the +1 to the gerrit contribution even after adding the review parameters 1 and +1. I gather that the Gerrit Reporting Values and Verified Commands are not set in this instance and therefore nothing is sent by the job to the gerrit instance & patch ? 

It should work out of the box. Please, open a ticket and we will investigate.

4-      This instance does not seem to have any executors pre-locked. Is/Will this be the future default configuration ? i.e. will they be dispatched by the kubernetes manager and assigned whenever a free node is available ?

As stated above, agents / executors are dynamically provisioned. You won't see any until you start a build. Up to 2 agents can be provisioned simultaneously for your Jenkins instance, i.e. you can run up to 2 jobs concurrently.


Mikaël Barbero 
Team Lead - Release Engineering | Eclipse Foundation
📱 (+33) 642 028 039 | 🐦 @mikbarbero
Eclipse Foundation: The Platform for Open Innovation and Collaboration

Attachment: signature.asc
Description: Message signed with OpenPGP

Back to the top