Think I found the issue, I had a much older version of the kube plugin
installed and since then, client caching was introduced, I am applying the
fix found here: https://github.com/jenkinsci/kubernetes-plugin/pull/429
On Thursday, July 18, 2019 at 9:41:24 AM UTC-4, Andres Galindo wrote:
>
&
1/raw/71a0a287923eca2e2050dcff5c25d39eb307ad6c/config.yaml
I was hoping someone had some experience with the above issue or some
insight as to where I should look into next?
Cheers,
Andres.
P.S. will do the 2.176.2 security update soon, just want to get this issue
figured out first.
--
You received this message because yo
Thanks for the feedback everyone, it was quite helpful.
Regards,
Andres
On Thursday, October 15, 2015 at 2:00:22 PM UTC-4, Brian Ray wrote:
>
> See this earlier thread for the Iterator serialization issue:
>
> https://groups.google.com/d/msg/jenkinsci-users/LGRv7Jq60YI/ZN-68zu
y docs
to figure out if the way I'm generating the closure is an issue. But
overall the state the system gets into seems to be pretty bad (can't abort
the job). So I wanted to send out an email here just in case this is a
problem with the Jenkins groovy core.
Thanks again for the con
4 jenkins related
> post.
>
>
> On Sat, Feb 22, 2014 at 3:45 PM, andres reynaldy
>
> > wrote:
>
>> Hi,
>>
>> I'm new to Jenkins and I'm wondering is this the user forum for jenkins?
>> I was expecting a forum, not a gmail mailing group. But a
Hi,
I'm new to Jenkins and I'm wondering is this the user forum for jenkins? I
was expecting a forum, not a gmail mailing group. But anyway, I'm here to
ask about the best practice about how to set up integration testing in
Jenkins. Do we deploy that as separate build job thats run after the co
I have a pom only project that is built by Jenkins. The only thing it
really does is send it to my repo. This is used by several other projects.
For some reason, Jenkins is not keeping these builds. It even seems to be
deleting the workspace. The subversion polling log shows: "No existing
b
