[JIRA] (JENKINS-41119) Not able to execute command on chef nodes parallely

2017-01-23 Thread irfu.sa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 irfan sayed resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Code fixed. issue was related to data binding and wrong method name  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-41119  
 
 
  Not able to execute command on chef nodes parallely
 

  
 
 
 
 

 
Change By: 
 irfan sayed  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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.go

[JIRA] (JENKINS-41119) Not able to execute command on chef nodes parallely

2017-01-23 Thread irfu.sa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 irfan sayed commented on  JENKINS-41119  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Not able to execute command on chef nodes parallely
 

  
 
 
 
 

 
 This is fixed. closing now...  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-41119) Not able to execute command on chef nodes parallely

2017-01-16 Thread irfu.sa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 irfan sayed commented on  JENKINS-41119  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Not able to execute command on chef nodes parallely
 

  
 
 
 
 

 
 working on this.  The configuration issue has been fixed. now working on the command execution   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-41119) Not able to execute command on chef nodes parallely

2017-01-16 Thread irfu.sa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 irfan sayed created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41119  
 
 
  Not able to execute command on chef nodes parallely
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 irfan sayed  
 
 
Components: 
 sinatra-chef-builder-plugin  
 
 
Created: 
 2017/Jan/17 6:10 AM  
 
 
Labels: 
 plugin  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 irfan sayed  
 

  
 
 
 
 

 
 Even after saving the configuration , the chef-client OR any another command (as per configuration) is not able to run on the targetted nodes. This is critical and imapcting the plugin execution  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

 

[JIRA] [core] (JENKINS-18571) clicking on build now button fires build twice for specific jobs

2013-07-08 Thread irfu.sa...@gmail.com (JIRA)














































irfan sayed
 commented on  JENKINS-18571


clicking on build now button fires build twice for specific jobs 















job type is freestyle
all the jobs are configured with parameterized build

i have upgraded jenkins to 1.521 and issue seems resolved. however, please verify 

regards
irfan



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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/groups/opt_out.
 
 


[JIRA] [core] (JENKINS-17858) does not allow defaulting to specifig instance

2013-07-04 Thread irfu.sa...@gmail.com (JIRA)














































irfan sayed
 updated  JENKINS-17858


 does not allow defaulting to specifig instance
















Change By:


irfan sayed
(05/Jul/13 4:02 AM)




Labels:


lts-candidate



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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/groups/opt_out.
 
 


[JIRA] [active-directory] (JENKINS-18571) clicking on build now button fires build twice for specific jobs

2013-07-02 Thread irfu.sa...@gmail.com (JIRA)














































irfan sayed
 commented on  JENKINS-18571


clicking on build now button fires build twice for specific jobs 















further, i verified the logs but nothing is mentioned as such
please suggest 

regards



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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/groups/opt_out.
 
 


[JIRA] [active-directory] (JENKINS-18571) clicking on build now button fires build twice for specific jobs

2013-07-01 Thread irfu.sa...@gmail.com (JIRA)














































irfan sayed
 created  JENKINS-18571


clicking on build now button fires build twice for specific jobs 















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


active-directory



Created:


02/Jul/13 4:42 AM



Description:


hi,

i have recently updated Jenkins server from 1.515 to 1.520 
in 1.520, there is one fix Build Now” link did not work for multijobs. (issue 16974). i was also facing same issue in 1.515 so thought i should update to 1.520.
after upgrade, the issue got resolved and i was able to fire the build. however, i have seen for some jobs, build got fired twice. everytime, i have to cancel the second build and let the first build goes as is.

this is critical and confusing for dev community. whenever they fire the build, it get fired twice and they have to cancel either of them 

please have a look.

regards
irfan






Due Date:


12/Jul/13 12:00 AM




Environment:




Jenkins master : 1.520 , server : RHEL : 5.5 



following are the plugins installed and their corresponding versions 



conditional buildstep - 1.2.2

credential plugin - 1.4

extended choice parameter plugin - 0.28

jenkins active directory plugin - 1.33

jenkins email extension plugin - 2.30.2

jenkins mailer plugin - 1.5

parameterized trigger plugin - 2.18

ssh - 2.3

perforce - 1.3.24

run condition - 0.10 

ssh agent - 1.0 

ssh credentials - 0.3 

ssh slaves - 0.25

static analysis utilities - 1.49 

token macro - 1.7 






Fix Versions:


current



Project:


Jenkins



Priority:


Major



Reporter:


irfan sayed

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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/groups/opt_out.
 
 


[JIRA] [email-ext] (JENKINS-18433) getting exception when configuring email-ext

2013-06-20 Thread irfu.sa...@gmail.com (JIRA)














































irfan sayed
 commented on  JENKINS-18433


getting exception when configuring email-ext















thanks a lot
it's resolved

regards
irfan



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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/groups/opt_out.
 
 


[JIRA] [email-ext] (JENKINS-18433) getting exception when configuring email-ext

2013-06-20 Thread irfu.sa...@gmail.com (JIRA)














































irfan sayed
 commented on  JENKINS-18433


getting exception when configuring email-ext
















please refer below

Status Code: 500

Exception: java.lang.NullPointerException
Stacktrace:
javax.servlet.ServletException: java.lang.NullPointerException
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:719)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:214)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
	at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64)
	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:76)
	at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:240)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:164)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:462)
	at org.apache.catalina.core.StandardHostValve.invoke(Standa

[JIRA] [email-ext] (JENKINS-18433) getting exception when configuring email-ext

2013-06-20 Thread irfu.sa...@gmail.com (JIRA)














































irfan sayed
 created  JENKINS-18433


getting exception when configuring email-ext















Issue Type:


Bug



Assignee:


Alex Earl



Attachments:


email-ext.bmp



Components:


email-ext



Created:


20/Jun/13 5:13 PM



Description:


getting following exception while configuring email ext

in the global config, i have defined the smtp server address also 
still getting this exception. 

please suggest 

regards




Due Date:


21/Jun/13 12:00 AM




Environment:


Hudson server : RHEL 5.5 

jenkins version : 1.515



email-ext version : 2.30.2








Project:


Jenkins



Priority:


Major



Reporter:


irfan sayed

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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/groups/opt_out.