[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cbi-dev] [CJE] How to know why a pod isn't properly provisioned?
|
Hi Mickael,
Unfortunately, the Jenkins Kubernetes plugin is really bad at providing information about the pod provisioning and for the foreseeable future, we cannot grant you access to the cluster to poke at the logs. I'd suggest you open a ticket against the project https://issues.jenkins-ci.org/secure/Dashboard.jspa. Feel free to also open a ticket on the EF bugzilla with links to the failing jobs and instruction about how to start it safely (e.g., if it has parameters) and we will do the background work to provide you with some details.
Cheers,
Mikaël Barbero
Team Lead - Release Engineering | Eclipse Foundation 🐦 @mikbarbero
Hi all,
I'm struggling with an update of the pod/containers for the Wild Web Developer build from Jenkinsfile. I'm only trying to update one docker image, so I'm changing the reference to that image and renaming the pod to ensure I don't get an older version: https://github.com/eclipse/wildwebdeveloper/pull/334 . However, the build never start, waiting for an executor.
My question is how can I get info about what's wrong at provisioning? The amount of feedback I see is clearly insufficient (or maybe even nonexistent) to help troubleshooting such a trivial change, it's very frustrating.
Thanks in advance.
_______________________________________________ cbi-dev mailing list cbi-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cbi-dev
|
Attachment:
signature.asc
Description: Message signed with OpenPGP
