| 
Hi Mikael,   Thanks very much for all your answers ! I’ll process them and amend the configurations as I can and come back if I have
 further questions and I can’t find answers on my own J   Cheers,   
De : cbi-dev-bounces@xxxxxxxxxxx <cbi-dev-bounces@xxxxxxxxxxx>
De la part de Mikaël BarberoEnvoyé : vendredi 7 juin 2019 09:58
 À : Common-build Developers discussion <cbi-dev@xxxxxxxxxxx>
 Objet : Re: [cbi-dev] Interrogations on the new Jenkins/Kubernetes instances
   Hi Quentin, 
See my answers inline 
 
 
  
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: 
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 ? 
 
 
2-      I
 cannot seem to be able to run the zip command from a shell script build step. Should I use something else ? 
 
 
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. 
Team Lead - Release Engineering | Eclipse Foundation 
📱 (+33) 642 028 039 |
🐦 @mikbarbero   |