Re: Generate API Token does not display token to user.

2019-08-30 Thread Philip Mason
> > Identified a problem with the Permissive Script Security plugin version 0.5. > > This was the cause of the problem. Rolling back the plugin to version 0.3 solved the issue. - - - Philip -- You received this message because you are subscribed to the Google Groups "Jenkins Users"

Re: Generate API Token does not display token to user.

2019-08-29 Thread Philip Mason
> > Hi Mark, No proxy involved at any level ... Standard Chrome browser. But I've just discovered there's a potential problem writing to the user config files. hudson.model.User.save is hitting NPEs in the Cloudbees example token generation script, as well as occasionally when I re-login

Generate API Token does not display token to user.

2019-08-29 Thread Philip Mason
Hi Jenkins folks. Running LTS 2.176.3. I find that "Add New Token" in the user configuration page isn't working. "Generate" button creates token, but it is never displayed to the user. Have to refresh the page to see that the token was created. The Script Console suggestion from Cloudbees to

Re: kubernetes plugin 1.15.1 deletes the pod yaml specified in "Manage Jenkins" Cloud section.

2019-04-22 Thread Philip Mason
Thanks! On Mon, Apr 22, 2019 at 11:45 AM Carlos Sanchez wrote: > this has been fixed in 1.15.2 > https://issues.jenkins-ci.org/browse/JENKINS-57112 > > On Thu, Apr 18, 2019 at 9:13 PM Philip Mason wrote: > >> Hi, >> >> I installed the latest kubernetes plugi

kubernetes plugin 1.15.1 deletes the pod yaml specified in "Manage Jenkins" Cloud section.

2019-04-18 Thread Philip Mason
Hi, I installed the latest kubernetes plugin 1.15.1 and found that all of my container pod yaml snippets were deleted and anything I put in the text box is no longer persisted. I'm using this means of specifying the pod yaml since legacy non-pipeline jobs can then use the slaves spun up in my

transitioning between non-cloud and cloud-based worker nodes. Node restrictions?

2019-04-18 Thread Philip Mason
Hi, I am starting to ramp up some kubernetes cluster based worker nodes into an existing Jenkins master that uses Node Restrictions and labels to keep certain hands off of resources that aren't allotted to them. I have a mixture of non-pipeline and pipeline projects. I noticed the