|Re: [cbi-dev] Interrogations on the new Jenkins/Kubernetes instances|
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
Description: Message signed with OpenPGP