Re: Generate API Token does not display token to user.
> > 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" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/96180a85-6d97-4a16-bcff-4e36cf79823d%40googlegroups.com.
Re: Generate API Token does not display token to user.
> > 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 to a old session like this: java.lang.NullPointerException at hudson.Util.fileToPath(Util.java:1501) at hudson.model.UserIdMapper.createDirectoryForNewUser(UserIdMapper.java:145) at hudson.model.UserIdMapper.putIfAbsent(UserIdMapper.java:92) at hudson.model.User.putUserFolderIfAbsent(User.java:806) at hudson.model.User.constructUserConfigFile(User.java:802) at hudson.model.User.save(User.java:796) at jenkins.security.LastGrantedAuthoritiesProperty.update(LastGrantedAuthoritiesProperty.java:81) at jenkins.security.LastGrantedAuthoritiesProperty$SecurityListenerImpl.loggedIn(LastGrantedAuthoritiesProperty.java:112) at jenkins.security.SecurityListener.fireLoggedIn(SecurityListener.java:129) at hudson.security.AuthenticationProcessingFilter2.onSuccessfulAuthentication(AuthenticationProcessingFilter2.java:106) at org.acegisecurity.ui.AbstractProcessingFilter.successfulAuthentication(AbstractProcessingFilter.java:486) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:266) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:90) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:540) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:524) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1701) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1345) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:480) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1668) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1247) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.Server.handle(Server.java:502) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:370) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:267) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:427) at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:321) at org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:159) at
Generate API Token does not display token to user.
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 generate a token for a user throws an NPE at user.save(). - - - Philip -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/77cca0af-1244-4193-94fe-7e87d9de9a98%40googlegroups.com.
Re: kubernetes plugin 1.15.1 deletes the pod yaml specified in "Manage Jenkins" Cloud section.
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 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 Kubernetes cluster. >> >> Also, I needed to bump up the ephemeral-storage request in order to >> successfully run on nodes that have been running for a long time. >> >> Is there another place I'm supposed to specify the yaml - other than by >> using declarative/scripted pipelines? >> >> Thanks, >> >> - - - Philip >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to jenkinsci-users+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/171ef771-0b69-48ac-a2a8-985f23062e5b%40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-users/171ef771-0b69-48ac-a2a8-985f23062e5b%40googlegroups.com?utm_medium=email_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-users/V_Kxbe1RQ_U/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/CALHFn6Ma2hf2XuKarwKw98xB%2BWS%2BB%2BJ3KDDOj-aK01ozjh3Fjw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-users/CALHFn6Ma2hf2XuKarwKw98xB%2BWS%2BB%2BJ3KDDOj-aK01ozjh3Fjw%40mail.gmail.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAD9GMuHj2S9H0KYEPjLRw0227xBTjKxrmQrYA9e%2BrUStfvKrfA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
kubernetes plugin 1.15.1 deletes the pod yaml specified in "Manage Jenkins" Cloud section.
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 Kubernetes cluster. Also, I needed to bump up the ephemeral-storage request in order to successfully run on nodes that have been running for a long time. Is there another place I'm supposed to specify the yaml - other than by using declarative/scripted pipelines? Thanks, - - - Philip -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/171ef771-0b69-48ac-a2a8-985f23062e5b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
transitioning between non-cloud and cloud-based worker nodes. Node restrictions?
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 kubernetes plugin could cooperate with settings in folders to restrict the use of the cloud to certain pipeline projects. In the Node configure dialog, with the Node Restriction option, I could specify a regex of all of the projects that were allowed to access the Node. The Node Restriction option is blank for nodes spun up into kubernetes. Besides recasting all of my non-pipeline projects into pipeline projects, is there another way to get the same effect? Or a better way in general to handle this? Project specific labels for nodes and different pod templates for each project? Thanks, - - - Philip -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6625f51c-3483-4801-acc4-57392cadb4f4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
