--prow). Containers using
jenkinsfile-runneror Tekton are run and pod logs are optionally copied to permanent storage (as per
jx get storage) when the build completes. Very different from JEP-207/210/212, which deals with regular Jenkins servers that should upload logs of potentially in-progress builds from agents to external storage and (as needed) retrieve from storage to the master.
Hey, I'm looking to add support for kubevirt (https://github.com/kubevirt/kubevirt) VMs as dynamic Jenkins agents on K8s (similar to the existing
kubernetes-plugin). I wonder if there is a place to extend the current plugin and maybe add another provider along with the existing pod... since all the infra code will be the same and the difference is only in the kind of the object we request from K8s and the arguments it accepts...
I understand that it will require some refactoring to let users choose the kind of the object he wants to provision, and the alternative is to maintain a plugin which is 90% the same as the existing one
inheritFromstatement in the stage's agent configuration? I tried to use the label, but then the inheritance seems to be ignored, and the stage pod only contains the containers from its own template. I have more details and an example in this stack overflow question: https://stackoverflow.com/questions/58709163/jenkins-kubernetes-plugin-declarative-pipeline-and-pod-template-inheritance
Hi All, I am new to jenkins and using enkins ver. 2.190.2 which is installed in Azure Kubernetes version 1.14.6 . I am trying to export the jenkins jobs using the command line using a simple script by passing the job name. Export_jobs()
while read -r i
java -jar jenkins-cli.jar -s $URL -auth $username:$password get-job "$i" </dev/null > JOB/$i.xml
done < list_jobs.txt