|We are experimenting now with unique pod labels. For now this looks as if this seems to work. We are preparing now PRs to apply that to our branches. If this is solving the issue this could be worth an entry to the CBI Troubleshooting FAQ. I’ll keep you posted.|
Hi,Isn't https://issues.jenkins-ci.org/browse/JENKINS-47759 which Christianhttps://bugs.eclipse.org/bugs/show_bug.cgi?id=548573#c6 the explanationfor the strange behavior? Did you test it with unique pod labels?Regards,FredOn 25.06.19 09:58, Karsten Thoms wrote:
Dear CBI users,-- Frederic GurrRelease Engineer | Eclipse Foundation Europe GmbHAnnastr. 46, D-64673 ZwingenbergHandelsregister: Darmstadt HRB 92821Managing Directors: Ralph Mueller, Mike Milinkovich, Chris Laroque_______________________________________________cbi-dev mailing listcbi-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visithttps://www.eclipse.org/mailman/listinfo/cbi-dev
we from the Xtext team are observing a strange issue with our build jobs
on CBI. We have set up multibranch pipeline jobs for our builds and are
currently experimenting with different resource requirements .
Therefore we are doing changes to our POD configurations in Jenkinsfiles.
The issue now is that the branch jobs often do not use the POD
configuration as defined in the Jenkinsfile: We see other resource
requirements or none printed to the job’s log output. For us it looks a
bit random which configuration is actually used. We would expect that
the Jenkinsfile’s POD configuration should reliably be used for the job
execution. We have opened bug#548573  to track this.
Does anyone have similar experience with custom POD configurations, or
ideally an explanation?
cbi-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit