|Re: [cbi-dev] Interrogations on the new Jenkins/Kubernetes instances|
I tried correcting the points mentioned but found other problems. Again, if you could help me with them itâd be a great help:
1- The first point I made was mainly about keeping the workspace for the downloaded maven dependencies which can be a pain to download every single time.(which, if I understood correctly will be the case if the workspace is deleted every single time)
2- I tried to add a promote step to the job but I cannot figure out how one would access the archive files from the job as the promote step is launched in another agent. I gather you can get them through a (curl ?) request but that can be a big overhead for larger project archives (e.g. RCPs, zipped p2s containing hundreds of plugins, â). There must be a way to do it cleanly but I didnât find how.
3- I tried to publish the contents in the same workspace state (after the build) but the ssh connection did not seem to get through (no error shown just a timeout).
Is the destination still /home/data/httpd/download.eclipse.org or should I call another destination ?
As a bonus question it should be possible to use variables in the request but if I transform âssh genie.shared@xxxxxxxxxxxxxxxxxxxxxxxxxxxx mkdir âp /home/data/***â into âssh $sshGenie@$sshRemote mkdir -p $destinationUpdateSiteâ it times out. Is it because the previously mentioned destination is erroneous ?
Ps : The zip command seem to only be available in the âmigrationâ profile. Should I open a bug for it to be integrated inside the âui-testâ (as I get the feeling that migration is not supposed to last) along the one for Gerrit problems ?
Pps: to provide further information I included the script I intended to use as a promotion script. If you see any kind of problems with it feel free to tell me J
See my answers inline
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 (https://wiki.eclipse.org/Jenkins#How_do_I_deploy_artifacts_to_download.eclipse.org.3F). Note that if you push files that are not releases, you should put them in a folder strcuture that will not be mirrored (see https://wiki.eclipse.org/IT_Infrastructure_Doc#Use_mirror_sites.2Fsee_which_mirrors_are_mirroring_my_files.3F for the list of file patterns that are not send to mirrors).
"zip" command is not available in the default agent image, "unzip" is though. Advanced images are available in "migration" and "ui-test" agents. See https://wiki.eclipse.org/CBI/Jenkins_Migration_FAQ#How_do_I_run_UI-tests_on_the_new_infra.3F for how to use them.
It should work out of the box. Please, open a ticket and we will investigate.
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
Eclipse Foundation: The Platform for Open Innovation and Collaboration