[JIRA] (JENKINS-17514) NullPointerException: no workspace from node hudson.slaves.DumbSlave after upgrade to 1.510

2017-03-22 Thread jothibasu.kama...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 jothibasu k edited a comment on  JENKINS-17514  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NullPointerException: no workspace from node hudson.slaves.DumbSlave after upgrade to 1.510   
 

  
 
 
 
 

 
  we are using maven plugin and slave is connected as Windows Slave, in the middle of the maven execution build got aborted due to same error, Could you please check and let me know this error is related to this issue or different.{code:java}ERROR: Build step failed with exceptionjava.lang.NullPointerException: no workspace from node hudson.slaves.DumbSlave[Maventest-01] which is computer hudson.slaves.SlaveComputer@3c2ce65f and has channel null at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:74) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:64) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.build(MavenModuleSetBuild.java:906) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:857) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Build step 'Execute Windows batch command' marked build as failureERROR: Maventest-01 is offline; cannot locate Maven 3.0.4ERROR: Maventest-01 is offline; cannot locate Maven 3.0.4ERROR: Failed to parse POMsjava.io.IOException: Backing channel is disconnected. at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:184) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:249) at com.sun.proxy.$Proxy114.isAlive(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:996) at hudson.maven.ProcessCache$MavenProcess.call(ProcessCache.java:166) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:840) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Build did not succeed and the project is configured to only push after a successful build, so no pushing will occur.Finished: FAILURE{code}our Jenkins Version is : Jenkins ver. 1.651.3.1 (CloudBees Jenkins Enterprise 16.06)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  

[JIRA] (JENKINS-17514) NullPointerException: no workspace from node hudson.slaves.DumbSlave after upgrade to 1.510

2017-03-22 Thread jothibasu.kama...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 jothibasu k commented on  JENKINS-17514  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NullPointerException: no workspace from node hudson.slaves.DumbSlave after upgrade to 1.510   
 

  
 
 
 
 

 
  we are using maven plugin and slave is connected as Windows Slave, in the middle of the maven execution build got aborted due to same error, Could you please check and let me know this error is related to this issue or different. 

 

ERROR: Build step failed with exception
java.lang.NullPointerException: no workspace from node hudson.slaves.DumbSlave[Maventest-01] which is computer hudson.slaves.SlaveComputer@3c2ce65f and has channel null
	at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:74)
	at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:64)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.build(MavenModuleSetBuild.java:906)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:857)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
	at hudson.model.Run.execute(Run.java:1738)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529)
	at hudson.model.ResourceController.execute(ResourceController.java:98)
	at hudson.model.Executor.run(Executor.java:410)
Build step 'Execute Windows batch command' marked build as failure
ERROR: Maventest-01 is offline; cannot locate Maven 3.0.4
ERROR: Maventest-01 is offline; cannot locate Maven 3.0.4
ERROR: Failed to parse POMs
java.io.IOException: Backing channel is disconnected.
	at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:184)
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:249)
	at com.sun.proxy.$Proxy114.isAlive(Unknown Source)
	at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:996)
	at hudson.maven.ProcessCache$MavenProcess.call(ProcessCache.java:166)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:840)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
	at hudson.model.Run.execute(Run.java:1738)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529)
	at hudson.model.ResourceController.execute(ResourceController.java:98)
	at hudson.model.Executor.run(Executor.java:410)
Build did not succeed and the project is configured to only push after a successful build, so no pushing will occur.
Finished: FAILURE
 

 our Jenkins Version is : Jenkins ver. 1.651.3.1 (CloudBees Jenkins Enterprise 16.06)  
 

  
 
 
 
 

 
 
 

 
  

[JIRA] [matrix-auth-plugin] (JENKINS-23844) Matrix based security should apply to case insensitive user name.

2015-06-02 Thread jothibasu.kama...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jothibasu k updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-23844 
 
 
 
  Matrix based security should apply to case insensitive user name.  
 
 
 
 
 
 
 
 
 

Change By:
 
 jothibasu k 
 
 
 

Issue Type:
 
 Improvement Bug 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [matrix-auth-plugin] (JENKINS-23844) Matrix based security should apply to case insensitive user name.

2015-06-02 Thread jothibasu.kama...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jothibasu k commented on  JENKINS-23844 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Matrix based security should apply to case insensitive user name.  
 
 
 
 
 
 
 
 
 
 
Please check on this... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [matrix-auth-plugin] (JENKINS-23844) Matrix based security should apply to case insensitive user name.

2015-06-02 Thread jothibasu.kama...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jothibasu k updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-23844 
 
 
 
  Matrix based security should apply to case insensitive user name.  
 
 
 
 
 
 
 
 
 

Change By:
 
 jothibasu k 
 
 
 

Priority:
 
 Major Blocker 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [active-directory-plugin] (JENKINS-12607) Active directory user names should not be case sensitive.

2015-06-02 Thread jothibasu.kama...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jothibasu k updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-12607 
 
 
 
  Active directory user names should not be case sensitive.   
 
 
 
 
 
 
 
 
 

Change By:
 
 jothibasu k 
 
 
 

Priority:
 
 Minor Blocker 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [active-directory-plugin] (JENKINS-12607) Active directory user names should not be case sensitive.

2015-06-02 Thread jothibasu.kama...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jothibasu k commented on  JENKINS-12607 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Active directory user names should not be case sensitive.   
 
 
 
 
 
 
 
 
 
 
Guys any update on this issue... we facing this issue while trying to integrate with JIRA..Please check 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [matrix-auth-plugin] (JENKINS-23844) Matrix based security should apply to case insensitive user name.

2015-05-25 Thread jothibasu.kama...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jothibasu Kamaraj commented on  JENKINS-23844 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Matrix based security should apply to case insensitive user name.  
 
 
 
 
 
 
 
 
 
 
 Any Progress on this issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [active-directory-plugin] (JENKINS-12607) Active directory user names should not be case sensitive.

2015-05-25 Thread jothibasu.kama...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jothibasu Kamaraj edited a comment on  JENKINS-12607 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Active directory user names should not be case sensitive.   
 
 
 
 
 
 
 
 
 
 Any Fix is  give  given  for this issue ,we are also facing same issue due to Case Sensitive while trying to apply the Access for the jobs via Role Strategy or Matrix Based security. Jenkins Version:1.596.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [active-directory-plugin] (JENKINS-12607) Active directory user names should not be case sensitive.

2015-05-25 Thread jothibasu.kama...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jothibasu Kamaraj commented on  JENKINS-12607 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Active directory user names should not be case sensitive.   
 
 
 
 
 
 
 
 
 
 
Any Fix is give for this issue ,we are also facing same issue due to Case Sensitive while trying to apply the Access for the jobs via Role Strategy or Matrix Based security. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.