[JIRA] [matrix-auth-plugin] (JENKINS-30495) Add 'authenticated' user group to the Matrix UI

2015-09-16 Thread cmil...@appnexus.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Miller created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30495 
 
 
 
  Add 'authenticated' user group to the Matrix UI  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 

Components:
 

 matrix-auth-plugin 
 
 
 

Created:
 

 16/Sep/15 3:13 PM 
 
 
 

Environment:
 

 Jenkins ver. 1.609.2 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Christopher Miller 
 
 
 
 
 
 
 
 
 
 
In a nutshell: it'd be nice if the jelly script that generates the matrix ui element included a row for the 'authenticated' user group in addition to the anonymous user. (I'd even go so far as to advocate replacing 'anonymous' with 'authenticated' as the lone persistent row of the matrix, but that's a bit opinionated.) 
My reasoning for this is simple: in my org many teams have jenkins projects that don't require strict authentication. Sometimes these teams would like to allow anyone in the organization to be able to configure a project, simply because the potential security impact of opening up the project's configs is so low compared to the inconvenience of having to maintain valid auth settings for it. To do this, most users simply give configure privleges to anonymous, because it's there and it gets the job done. Most of them don't realize that 'anonymous' includes non-logged in users, thus opening up their jobs to users who aren't even authenticated. 99% of them don't even know that the 'authenticated' user group exists, let 

[JIRA] [envinject-plugin] (JENKINS-27382) EnvInject plugin passes astrisk to Gradle plugin

2015-08-07 Thread cmil...@appnexus.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Miller commented on  JENKINS-27382 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: EnvInject plugin passes astrisk to Gradle plugin  
 
 
 
 
 
 
 
 
 
 
We just upgraded from 1.90 to 1.94 and the problem cropped up. Going to rollback to 1.90. This makes the sensitive variable functionality useless outside of the Execute Shell step. The password is passed as  to all other plugins that make use of the EnvVars object. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [ssh-agent-plugin] (JENKINS-29062) IncompatibleClassChangeError; AgentServer.safelyClose

2015-07-13 Thread cmil...@appnexus.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Miller commented on  JENKINS-29062 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: IncompatibleClassChangeError; AgentServer.safelyClose  
 
 
 
 
 
 
 
 
 
 
Update: seems that upgrading the JDK version on the slaves in question to Java 7 fixes this problem. The wiki page for the plugin mentions this, but for whatever reason we haven't hit this problem running java 6 up until today.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [ssh-agent-plugin] (JENKINS-29062) IncompatibleClassChangeError; AgentServer.safelyClose

2015-07-13 Thread cmil...@appnexus.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Miller commented on  JENKINS-29062 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: IncompatibleClassChangeError; AgentServer.safelyClose  
 
 
 
 
 
 
 
 
 
 
I've also experienced this on some of my slaves as well. Full stack trace from my logs if it's anymore useful. This stack trace comes up in the build logs after all of the build steps succeed.  

 

FATAL: java.io.IOException: Remote call on MyJenkinsSlave failed
hudson.remoting.RemotingSystemException: java.io.IOException: Remote call on MyJenkinsSlave failed
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:195)
	at com.sun.proxy.$Proxy89.stop(Unknown Source)
	at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper$SSHAgentEnvironment.tearDown(SSHAgentBuildWrapper.java:360)
	at hudson.model.Build$BuildExecution.doRun(Build.java:171)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536)
	at hudson.model.Run.execute(Run.java:1741)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:98)
	at hudson.model.Executor.run(Executor.java:374)
Caused by: java.io.IOException: Remote call on MyJenkinsSlave failed
	at hudson.remoting.Channel.call(Channel.java:761)
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:179)
	... 8 more
Caused by: java.lang.IncompatibleClassChangeError
	at com.cloudbees.jenkins.plugins.sshagent.jna.AgentServer.safelyClose(AgentServer.java:216)
	at com.cloudbees.jenkins.plugins.sshagent.jna.AgentServer.close(AgentServer.java:146)
	at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgent.stop(JNRRemoteAgent.java:109)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:326)
	at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:301)
	at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:260)
	at hudson.remoting.UserRequest.perform(UserRequest.java:121)
	at hudson.remoting.UserRequest.perform(UserRequest.java:49)
	at hudson.remoting.Request$2.run(Request.java:325)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)
	at ..remote call to MyJenkinsSlave(Native Method)
	at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1360)
	at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)
	at hudson.remoting.Channel.call(Channel.java:753)
	... 9 more

 

 
 
 
 
 
 
 
 
 
 
 
 
 

 

[JIRA] [sauce-ondemand-plugin] (JENKINS-29354) Sauce Ondemand Plugin 1.30 JSONException on Admin Config page submit

2015-07-10 Thread cmil...@appnexus.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Miller created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-29354 
 
 
 
  Sauce Ondemand Plugin 1.30 JSONException on Admin Config page submit  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Kohsuke Kawaguchi 
 
 
 

Components:
 

 sauce-ondemand-plugin 
 
 
 

Created:
 

 10/Jul/15 8:23 PM 
 
 
 

Environment:
 

 Jenkins 1.609.1 LTS  Sauce Ondemand Plugin: 1.30 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Christopher Miller 
 
 
 
 
 
 
 
 
 
 
I recently upgraded the LTS version of Jenkins, along with several plugins. I'd tested this upgrade earlier in the week with Sauce Ondemand Plugin v1.29 on a sandbox Jenkins master, but didn't notice that there was a new version of this plugin slated to be downloaded through the update center. Upon upgrading if I go to the Admin config panel and hit Save/Apply I get the stack trace posted below. Luckily it seems that any config changes I make do go through (thus not warranting a major priority marker imo), but the error is still annoying. 
I'm uninstalling this version and installing the 1.29 version by hand for now as a workaround. I've tested 1.30 on my sandbox Jenkins master and found the same problem, so I'm pretty sure this is specific to the 1.30 release. 

 

javax.servlet.ServletException: net.sf.json.JSONException: